Re: Re: [PATCH] Swixml - Extending DefaultFactory

There is a crucial  difference between extending tags through code and 
through XML. if I do it in XML I can generate everything on the fly. If 
it requires a class to register the tags then I have to code that in 
advance, and haul that class around to any apps I reuse a layout in... 
plus whenever I add a new tag to something I have to recompile that tag 
registering class. Given, this isn't really that much work, but it 
limits me and slows me down...and the whole point of SWIXML is to 
remove the need to write hundreds of lines of mind numbingly stupid 
swing code to register this and set that.... but if I want a new tag, 
well then now I have to do the same thing only for SWIXML this time 
instead of swing... fortunately with SWIXML it's only a few lines here 
and there not hundreds...but the point is I use swixml so I don't have 
to do that stuff in code. I want it flexible and easy to change on the 
fly. I mean 90% of my XML that SWIXML processes is generated on the fly 
based on whatever data happens to be floating through our systems.

-Kate

On Friday, October 24, 2003, at 02:28 PM, Wolf Paulus wrote:

> 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.