--- Gerald Bauer <[EMAIL PROTECTED]> wrote: > >> 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 > Excelent. Thanks, but most of those are XUL tools. The conversation was on non-XUL specific tools like Axualize. I see there are a couple there, certainly not the _many_ I was looking for. :) > > I will add your XML UI motor shortly. Great. > > If you want to evangelize Luxor/XUL, check out my > talks slides @ > http://luxor-xul.sourceforge.net/post/events.html did that. > > 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 XUL is simply a dialect. I dialect which could easily be incoperated into Axualize. Axualize is much more then just a UI motor. It's an application motor. > > 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 I beleive this is a weakness of XUL engines in general, as it build in the limitations of this archaic markup. Axuualize goes well beyond XUL motors in this respect by allowing much more flexible schemas. > speed-coding in a plain-vanilla text editor. You don't I work with develpers who code Axualize documents on plain vanilla text editors all the time. You don't need anything else. > need a GUI designer to untangle the unreadable You may want to read up on Axualize. Axualize xml is very simple to read. It is far simpler then plain vanilla JSR57. This is because Axualize includes aliases for classes/properties/methods. Look at some of the examples. They are not hard to read, even for those used to looking at HTML. > haystack dumped using Java Bean XML Schema > Persistance. > * Look at HP's Bluestone XwingML, a dead early XUL This product had a lot of good reasons to die, I won't go there. > 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. This is true, that is why Axualize goes far beyond this approach. > * Luxor's XUL markup is not tied to Sun's Swing GUI Neither is Axualize. Axualize is only bound by the platform on which it is implemented. Right now that is Java, but it could be anything. > 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
Axualize is only bound by the platform on which it is implemented. Right now that is Java, but it could be anything. I am currently working on a native Linux GCC port, and one of my developers is moving quickly to get a Python port going. > will be availabe for C#, Shark and other languages. > > - Gerald Hey Gerald, I can see you are very happy with XUL. But a lot of us have been there and done that, and found that for a lot of our needs XUL is just not enough, no matter if it is your favorite flavor, or mine. Axualize fills the same roles XUL does nicely and just as easily, and it does a whole lot more. One additional thing you forgot to mention in your FAQ. If you are already familiar with your favorite GUI toolkit, then learning something like XUL is just an extra step because it does not expose the power of the toolkit's API. Axualize does this. If this puts it beyond the reach of people who only want to learn HTML or HTML like dialects, well OK. In the end, to really make a UI kick, you have to understand what makes it tick. Those of us who are developing/using Axualize are doing so because we are filling niches which we have identified for ourselves. If LUXOR or any other XUL motor would have fit the bill, we would not have bothered. Remember Axualize is powerful enough to easily make XUL a subset. The reverse is not true. > > ______________________________________________________________________ > Post your free ad now! http://personals.yahoo.ca > > _______________________________________________ > Forum mailing list > [email protected] > http://mars.lunarpages.com/mailman/listinfo/forum_carlsbadcubes.com __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com
