Hello,
some major differences are:
xmlgui uses wrapper classes around swing widgets which
pre-set many default values and spacings. Reflection is
used to set most properties on swing widgets. Usually even
in a big program, you will not have one single "import javax.swing.."
statement over ten thousand lines of code.
It uses a very simple XML format, which is different
from Mozilla XUL and looks somewhat like this:
<widget class="Dialog" name="About">
<widget class="Button">
<property name="text" type="istring">common.sometext</property>
<emit event="clicked" name="quit"/>
</widget>
</widget>
What's also very different is the way the MVC pattern is used. An
input component can have a "key" property which it uses to "plug into"
the window's data model. So for example if you have a frame with a
text field, which has the key "text", you would write this to change
the text field's text:
dataModel.setValue("text", "someNewText");
So the complete state of any widget tree is always stored in a
data model, which can for example be serialized or loaded from
a J2EE value object.
Wenzel
> PS: If anyone has tried out Beryl, let us know what
> you think and how it compares to SwiXML, Luxor, XUI,
> Thinlet, and so on. Please post your comments to the
> xul-talk mailinglist.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
xul-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xul-talk
