I haven't investigated XForms much, but it seems...err...complicated.
It ain't, it's just that the spec was done more with implementors in mind than users (I think that's a bad move, but it doesn't reflect on the quality of the described technology).
XForms for HTML authors http://www.w3.org/MarkUp/Forms/2003/xforms-for-html-authors.html
What I really want is to be able to transparently edit server-side XML content (keeping the semantic structure of the XML itself) while interacting with the result of an XSL transformation.
That's what XForms does, except it's specified to be bidirectional instead of batch/monodirectional like XSLT. I'm not saying it's perfect, but you really sound like you'd want to taste it :)
I'd like to take time to implement it in Mozilla, it shoud be doable with XUL+js.
Things could be potentially simplified by performing the XSL transform within Mozilla, but then there wouldn't be a guarentee that the content would render the same in AxKit.
Nah, client-side XSLT is a PITA, especially if you're also using CSS.
-- Robin Berjon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
