RE: Illegal html in samples, with span outside of body

[Stefano Bagnara <ba...@ngi.it>]

> Again, this would look better if it was something like:
> 
> <html>
> <head> ... </head>
> <body jwcid="@MyAppsCustomBorderComponent,$content$">
> ...
> </body>
> </html>
> 
> That's conformant, but allows the border component to provide 
> the <html> and <head> (via @Shell) and
> <body> (via @Body).


Would the jwcid be an ordered list?
Should we use $content$ BEFORE the @MyAppsCustomBorderComponent?

If Tapestry will support multiple comma separated ids for a given tag
then I would suggest to suppport the standard "class" attribute for
tapestry ids, too.

Many commons visual html editors support editing of class elements and I
think it is html standard to have comma separated classes for a tag.
"*@*", "$*$" can be recognized by tapestry and a new convention for
named components (that are text only now). I'm not sure if @ and $ are
allowed as CSS class names, anyone knows?

Tapestry would then remove the recognized "classes".

I think a custom TemplateParser could allow this, am I right?

-b-