RE: When to use Thinlet/SwiXML

List for Users of Carlsbad Cubes' Technologies and Products schrieb am 06.07.04 08:59:11:
> 
> Thank you very much Kate.
> Now I am sure that I am not going to use Thinlet.
> But still I have one question in my mind that why people are using SwiXML
> though we have to write modelling class seperately for table, tree.
> 
> Is it worth to use SwiXML for Client-Server application(that includes add,
> edit, delete, list functionalities) having rich GUI?

Hello Bharat,

I imagine you like to have add, edit, delete, list functionalities in e.g. tables,
trees and the like. For this, Swing provides the MVC architecture. As you
noticed, you have to write that "M" part yourself, SwixMl does not help you
there. Furthermore, the "C" part lies also upon yourself. The thing SwixMl is
good at and helps you a great bunch is the "V" part.

I wrote some applictions with the functionalities you mentioned and SwixMl
helped me a lot: to separate responsibilities, for more flexibility and the like.
E.g. it is not that important if you have a JLabel or a JTextField to contain a
textual description of some sort. But without SwixMl, you have to import
the one or the other, have a variable/attribute created, have to take care
of I18N yourself (no, user-readable text in the code is not an option) and
the like. Additionally, the cycle of GUI creation and layout finetuning is
much slower with a real application: suppose you design a dialog which
is quite long to go to in your app. Either you code some nasty shortcut or
you have to go the long way all over again until you are pleased with the
layout. WIth SwixMl you just render the dialog-XML file in a test program
all over again.

Yours,

Frank
> 
> 
> Thanks again,
> Bharat Panchal
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of masukomi
> Sent: Tuesday, July 06, 2004 3:54 AM
> To: List for Users of Carlsbad Cubes' Technologies and Products
> Subject: Re: [Forum] When to use Thinlet/SwiXML
> 
> 
> > Thinlet Questions:
> > - Accroding to thinlet.dtd, you can not put button/checkbox in a table
> > cell.
> > So how to display a GUI that displays records as well as provide
> > facility
> > for editing or deleting it?
> 
> you make a button elsewhere then have it call a script that looks at
> the selected item in your table and through some code you've developed
> (usually some hash lookup with the text in the cells as the keys)
> figures out what Java object that corresponds to. Then you do something
> with it.
> 
> > - Can I write only one xml for list, add, edit, delete functionaly?
> 
> umm... can you rephrase the question?
> 
> >
> > SwiXML Questions:
> > - We have to write model for JTable and JTree ourselves. So what is the
> > advantage of using table and tree in SwiXML?
> 
> you can put a button / checkbox in a table cell. ;)
> Seriously thought. With thinlet you're limited to text in your tables.
> With SwiXml you can put practically any Swing object in there.
> 
> > Again I am new to this technology, so please excuse me if I am wrong
> > anywhere.
> > Can you please answer above questions and suggest when to use Thinlet
> > and
> > SwiXML?
> 
> Thinlet for simple quick things that don't require embedding anything
> more complex than text in a list or table and aren't going to need any
> functionality not explicitly offered by thinlet.
> 
> SwiXml for everything else.  You want power? You want extensibility?
> You want SwiXml.
> You want quick and simple with limited GUI functionality? Thinlet.
> 
>  From your description I think you're going to want SwiXml.
> 
> 
> -Kate Rhodes
> Open source consultant & Java developer
> http://www.masukomi.org
> 
> 
> _______________________________________________
> Forum mailing list
> [email protected]
> http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
> 
> 
> _______________________________________________
> Forum mailing list
> [email protected]
> http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com