Re: RE: Swixml and SAX, Jelly - Final Word ?

If I could, I would like to pause the Sax, Pull, etc. discussion for a 
while. I think everyone interested has had a chance to voice an 
opinion.
Everyone has his reasons for using Swixml (or any other XUL library) 
and I really do welcome all your suggestions and concerns.

That said, only a few experienced GUI developers have created 
reasonably sized Java application using Swixml, some of them are listed 
in the Acknowledgment on the Swixml.org Web site and obviously, 
opinions from those member are considered a little more ;-)

If the XML descriptor you are using is one MB or more - yours truly 
hadn't you in mind when creating Swixml.
If you deploy on a platform where Swixml / Swing is terribly slow - 
xmlpull won't help you much and you are better of replacing Swing 
altogether (with Thinlet for instance).
However, like I have said before, I'm working in the embedded space and 
therefore ALWAYS consider resource limitations.

The next Swixml update will have the long awaited and much improve 
layout  support.
Following that, a re-factoring of parser and engine will enable SWT. 
(Again - Swixml is going to support SWT)
Extending Swixml (call it plug-in architecture if you'd like) is going 
to enable the pre-fill Comboboxes and Tables with data through the XML 
descriptor.

That's what's in the pipeline and the xml-pull and sax discussion are 
probably not going to change this.
I'm very sorry if you find that disappointing. However, Swixml is 
carefully being developed over more than a year now and even after 
moving the source into a CVS things are probably not going to change 
all that much. (Again - Swixml is going to be moved into a CVS - I'm 
just not to sure about java.net anymore).

	Wolf Paulus

C a r l s b a d   C u b e s
mailto:[email protected]

CONFIDENTIALITY NOTICE:
This message is intended only for the use of the individual or entity 
to which it is addressed, and may contain information that is 
privileged, confidential and exempt from disclosure under applicable 
law.
If you are not the intended recipient, please contact the sender by 
reply email and destroy all copies of the original message.