>> There a many (I repeat _many_) projects out there, open-source as well >> as close source that already support those kind of things.
> Wow many... Some links would be great. I would like to evangelize some > of those folks. :) I try to keep track of all XUL/XML UI motors known to mankind (such as XWT, Luxor, JellySwing, SwingML, KoalaML, and more). Have a look at http://luxor-xul.sourceforge.net/post/links.html I will add your XML UI motor shortly. If you want to evangelize Luxor/XUL, check out my talks slides @ http://luxor-xul.sourceforge.net/post/events.html Before you try to proselytize me with your Java's Bean XML Persistance zealotry, Please, check out my Luxor FAQ entry entitled: "How does Luxor XUL differ from Java's Bean Persistance XML Schema?" @ http://luxor-xul.sourceforge.net/luxorfaq.html#persistance Here are the core points that set Luxor (and to a lesser extend Swix) apart from Axualize: * Luxor's XUL markup is designed like HTML for speed-coding in a plain-vanilla text editor. You don't need a GUI designer to untangle the unreadable haystack dumped using Java Bean XML Schema Persistance. * Look at HP's Bluestone XwingML, a dead early XUL dialect a la Java Bean XML Schema Persistance, and you will see that dumping the state of a bean 1:1 in XML is a dead end. * Luxor's XUL markup is not tied to Sun's Swing GUI toolkit, in the future support for alternative GUI toolkit such as Eclipse SWT, Trolltech Qt, Gnome Gtk+ and more will be available. * Luxor is not tied to Java, in the future engines will be availabe for C#, Shark and other languages. - Gerald ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca
