Re: When to use Thinlet/SwiXML

On Jul 6, 2004, at 12:14 AM, Bharat Panchal wrote:

> Is it worth to use SwiXML for Client-Server application(that includes 
> add,
> edit, delete, list functionalities) having rich GUI?

I don't really see how those functionalities or the fact that it is a 
client-server app have any bearing on SwiXml. The only thing there that 
really has anything to do with it is "having rich GUI". If you want a 
rich GUI and you want it in Swing then Yes SwiXml would be a good 
choice.  But as far as SwiXml goes it really doesn't matter *what* 
you're doing with the gui or how it's connecting.

Sorry if this sounds like I'm attacking, what I'm trying to do is point 
out that non-gui issues are being used to determine a gui toolkit. If 
you want to determine if SwiXml is right for you then set aside all the 
questions that have nothing to do with using GUIs or building GUIs. 
What's left are the things that fall into SwiXml's domain.

mozilla is a client server app... ATM's are client server apps... 
practically everything is a client server app these days and yet they 
have a huge variety of Interface needs.  What are your interface needs 
and are they things that Swing is well suited to handling? If so then 
SwiXml would probably be a good choice because it makes all Swing 
development easier.


-Kate Rhodes
Open source consultant & Java developer
http://www.masukomi.org