Re: Axualize (formerly Swang) - Another Java XML UI Motor
Lane Sharman <[email protected]>
| Newsgroups | gmane.comp.java.luxor-xul.user |
|---|---|
| Message-ID | <[email protected]> |
Greetings Gerald, I have not made the time to make a case for Conga to the luxor community. Mea culpa on that score and I will effort to remedy this if I can find the time in the bottle. You may want to take an independent look at Conga, formerly Bongo. Its aspirations, formulated before Swing, are much in line architecturally with what are the aims of luxor. I have been using Conga for about 6 years now and, as a result of so many complaints in the UI space last year, I spent a great deal of time on the packaging, documentation, and compatibility issues with jdk 1.4 ... ouch. http://opendoors.com/conga This is really Arthur Van Hoff's baby and I have been the custodial engineer since java 1. I think if you wanted to target a really great GUI tool instead of Swing, this would be a worthy bet. Conga's GUI models employ only the Java graphics engine. The widgets do use or subclass AWT or Swing. http://conga.opendoors.com/SchemaDrivenGui is a decent URL on schema-driven layouts http://opendoors.com/conga/2.2/docs/mvcGuide.pdf gives time-honored respect to the virtues of MVC. Conga is strictly a rich skin builder so it is somewhat opaque for the new developer to figure out how to pull the strings of a GUI presentation. Most importantly, Conga's builder is all about round-trip creation, maintenance, and updating to a property representation of a GUI. This same representation can be managed at run-time as well. This is where luxor and Conga share very common ground. One final observation. A GUI presentation is a visible product of a designer with skill sets different than those of a software engineer. Therefore, with Conga and its Builder, every effort has been made to make it possible to have the cake and eat it too: the designer uses the visual builder and the application programmer can manipulate the same representation thru Conga's extensive API set. I would love to spend more time with the luxor project but, as it stands now, my time is in a shrinking bottle. :). Kindest regards Lane Gerald Bauer wrote: >Hi, > > I found another Java XML UI motor named Axualize >headed by Russell White. > > You might wonna check it out at >http://sourceforge.net/projects/axualize > > Any thoughts are welcome. > > Spoiler ahead. Here's my take: > > > > > * Using Sun's Java long-term XML bean persistence >format is a distaster. The whole idea of XUL is to >make the UI markup compact and readable and most >important independent of the underlying UI toolkit. > > * Axualize follows the Curl model ( >http://www.curl.com ) and (ab)uses XML for everything >(including styling, object creation, procedural >programming and more). > > * Axualize has no separate "standard" style language >such as CSS to "tag tags". > > * Axualize has no separate scripting language such >as Python. Axualize has its own half-baked proceduarl >programming tags and ignores Jakarta Jelly or Sun's >JSTL. > > I guess I won't switch over to Axualize for now. > > - Gerald > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >luxor-xul-user mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/luxor-xul-user > > > -- Lane Sharman http://opendoors.com Conga, GoodTimes and Application Hosting Services http://opendoors.com/lane.pdf BIO ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf