See inline below,
James Mason wrote on 17/11/04 01:52 AM:
On Sun, 2004-11-14 at 02:34 +0100, Stephane Bailliez wrote: [snip...]
[snip again...]
I don't think JXTemplate can handle conditional attributes, but I would like to point out that in most cases there's a "false" value that can be used to keep the same behavior as leaving the parameter off. The most obvious example I can think of is the "selected" attribute for <option> tags. Both selected="" and selected="false" should be valid for the unselected options.
There are conditional constructs for IF and CHOOSE similar/mirrored from XSLT. There is also an enhanced version of forEach, macros for creating custom tags, lots of goodies overall.
One thing I don't think JXTemplate can handle (not sure on this) is outputting non-marked-up content. This would be a problem with CSS files, for example. I love the way the CSS theme is handled with the example application (I've copied the idea into another system I'm working on), so it would be a shame to lose that.
You can output non XML content from JX templates, just as long as your JX Template is a valid XML document. Same way you can output a comma-delimited data file from an XSLT transformation. So outputting CSS, Javascript, etc would not be a technical problem, but it might be ugly to do so.
Tim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
