Re: XAML, JNDC, etc

I like this line of thinking. Exactly the reason I
have been developing a plugin engine similar to that
of eclipse, yet much smaller, easier to use, and so
on. Does pretty much the same thing, just not nearly
as robust and complex. I tend to believe, however,
that for some reason too many developers believe that
bigger/better/more standard, (e.g. Struts) is always
the way to go and overlook many much better solutions.

--- Brennan Stehling <[email protected]> wrote:
> I for one would like SwixML to stay independent
> because the goal of the project is to stay
> simplistic.
>  Most technologies introduced by Sun try to be
> highly
> flexible and before you know it you have a mountain
> of
> classes and Javadoc to go through before you can do
> anything productive.
> 
> In contrast, SwixML is very small with under 30
> classes.  I also envision the ability to use more
> than
> one XUL library for a given Swing application. 
> Perhaps you like the fast prototyping that SwixML
> provides, but a few screens need some unique
> features
> not possible with SwixML.  At that point you can
> employ another XUL engine or code it directly in
> Java.
>  Your MVC design should provide proper separation to
> make this possible.
> 
> A big advantage of SwixML having such a small
> codebase
> is that it can be improved quickly without risking
> collapsing a mountain of code.
> 
> - Brennan
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Search - Find what you’re looking for faster
> http://search.yahoo.com
> 
> _______________________________________________
> Forum mailing list
> [email protected]
>
http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com


__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com