= "&" code ";" [amp]
comment = "<" "!" "--" (-("!" "--" ">") .)* ("!" "--" ">")? [comment] -> ""
comment = "<" "!" (-">" .)+ ">" [comment] -> ""
I made a <template_test> tag to check operations under different conditions (/templates, /files/templates, /~hypervariety/templates). Its styles and script are in the header of the document, so they're already loaded.
It appears that it works. Or maybe "if it appears then it worked." Whatever.
Now, as blogged, a <templates> tag that makes templates. But this one is based on Events (for the moment) and it's exportable. Exporting could use PHP to look for the templates start and end tags and then turn it into a script and a media, but even easier is to rig the Page tag to support it.
<templates> is now defined. Let's define a roundie.
That should be it. Let's try to make another
Prototyping a 'template editor' for Roundie. To 'be able to program' means to be able to see invisibles. "Foundational" is pretentious-talk for the same thing. To edit HTML, look at the invisible tags...to instruct the computer what to do 'Behind the Scenes', then put the instructions BtS!
Lots of HTML5 is now behind the scenes and cryptic. For example, table id template_editor is called <table id=template_editor> in one place, table#template_editor
in another place, and document.getElementById('template_editor')
still somewhere else.
Here's a <template_editor>. It's actually a table with some useful behavior, and each use of the tag can connect itself to any object in the page. We'll start by connecting to the prototypical Roundie template so it can be viewed and edited directly.
Property name | Property value | |
---|---|---|
Script name | Javascript | |
'Stremely cool! Now let's make a new roundie and point at it.
Now to consider a better way to do properties: set the attribute, but dont trap changes until the init. Also must say that templates defined INSIDE a page shouldn't affect the outside, at least when you're not using 'true' JS.