RE: [ULC-developer] TableTree

[Etienne Studer]

What I would like to remark is that people seem to subclass ULC components much more often than needed. ULC, as Swing, exposes its behavior/configuration in a Beans-style way. In most situations, injecting different models and different renderers, and in general setting different attribute values is sufficient. On top of that, Josh Bloch's "favoring composition over inheritance" suggestion works out very well in many scenarios.   Just my two cents worth, not a conrete solution to your problem, no time to provide a step-by-step example ;-)   Etienne   From: [EMAIL PROTECTED] on behalf of salva vilarrasa Sent: Wed 03.05.2006 07:50 To: ulc-developer@lists.canoo.com Subject: [ULC-developer] TableTree Hi all, I am implementing a little collector software that must call some web services and order the data in a Table. I think the best thing to use is a TableTree component. The problem is that I haven't find any example or a good document explaining the steps to be followed in order to build a consistent TableTree. I am not sure about the overall organization of classes. I have created a class extending a ULCTableTree as stated in the reference guide. But after I am not sure if I need a model (I think I need it only to personalize the DefaultTableTree, but not sure). I also have created a class extendind ITableTreeModel but i am not sure if I have to get the data in that class or to pass the data from another one....I am a little bit in trouble with the structure of ULCfor creating components in the best way. I think it is the same structure for a Table object or other ULC components, anyone has a good experience and can explain me with a simple step by step example or a better document in the documentation I have read near all the documents, but i am still a bit confused, thanks folks!