Re: Re: [PATCH] Swixml - Extending DefaultFactory

I do understand and appreciate the requests for structural changes and new
features for the next Swixml version. Swixml 2, (the development has already
started) will include or enable almost the things we have talked about in
this forum; to name the most important:

SWT support

Layout support (i.e. introduction of a new Layout tag)

Easier instantiation for tag implantations that use constructors other than
a default constructor (sending dynamic parameter instances to a tag
constructor)

Model instantiation and initialization through XML for mostly static widget
model data (i.e. combo boxes, with static data).

Improved support for custom tags and tag libraries (plug-ability).

Etc.



However, all these things will be implemented in a way fitting the overall
Swixml strategy.



Regarding Gerald's comment, I'd like to point out that even with the current
Swixml release, there is no need to recompile or "tweaking the kernel" to
plug-in your own tags. The Swixml site shows in one of the samples how to
implement your own tags:

http://www.swixml.org/samples/index.html

6. Extend the Swixml TagLibrary with your own tags



getTaglib().registerTag( "xpanel", XPanel.class );

Which allows for compile-time type checking, an advantage one does not have
in scripting languages. Swixml exposes its TagLibraries and allows for
modifications. To conclude, Swixml will grow in functionality but not in
size and it will expand into SWT space without becoming slower.Regards
Wolf Paulus--Wolf PaulusC a r l s b a d   C u b e
smailto:[email protected] NOTICE:This message is
intended only for the use of the individual or entity towhich 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 replyemail and destroy all copies of
the original message.