You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for providing a link to the demo page, I was looking for it in order to get a list of parsers and their output! 👍
The idea about the tag syntax seems ok, but I think that it might be more reasonable to have them as
body<#id>
- type: text
- class: my-class-one another-class
+ children
+ div
// etc.
Where the #id is optional, attributes as strings, child elements in their own section. Or alternatively
body<#id>
+attrbutes
- type: text
- class: my-class-one another-class
+ div<#id>
// etc.
// etc.
But with that another question arises - How will textual content be handled, especially those that have i, em, small, sub, etc tags in there, those formatting tags might cause quite some noice, especially when they don't have any particular meaning from the perspective of a symbol-tree
A simple HTML file tree view would allow users to jump around the currently edited template file.
A few notes:
TAG<#id><.class>
.<input type="text">
or just leave them with tags for nowBest regards
Kuba
The text was updated successfully, but these errors were encountered: