Re: 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