Juha Lindfors <[EMAIL PROTECTED]> wrote:
>
>Sooo... we have:
>
>the model, our beloved XML files
>the view, our kick ass Swing dynamic tab sheet tree thingy
>the control, which is da script language/the gui controls (combined
>view+control)
>
>Does that make sense to anyone else?
As I understand it, the model is currently a set of Java classes that
hide the XML from the GUI, but know how to read and write it. (These are
the classes that need to be made totally Swing-free, because they are
used on the server as well as in EJX.)
For GUI users, the XML is completely hidden - but to use XSLT means
either (i) having to write an EJX-oriented abstraction layer over it, or
(ii) having to accept that power-users dive into dealing with XML
directly. Probably implement (ii) first, (i) later (only if there's a
real need).
--
Justin Forder
