It could be argued that (in some cases) XMLC requires more
effort vs. writing classes to render commonly used UI elements. For instance, if the same exact list widget
appears on a dozen pages, the XMLC approach would require the UI designer to mockup
that same list on each page in which it will appear.
Perhaps I could mockup commonly-used UI components in their
own HTML “fragment” pages, compile them via XMLC, and create the
page at runtime consisting of multiple XMLC page objects.
Anyone have thoughts on doing this?
Is it straightforward to call multiple writeDOM() methods in
sequence to build the final page?
Thanks!
--
David Michaels <dkm@xxxxxxx>
Director of Web Engineering
PGP Corporation (650) 319-9009
