Re: [Tile-dev] a tale of 2 trees

[Tim B. <tre...@ho...>]

Eckhard Lehmann wrote:

>Jeff,
>
>actually I am using treeview quite a lot for the Tloona IDE 
>(www.tloona.tk) and underlying "Tmw" megawidgets (which are part of 
>Tloona only). X scroll would be fine, but in general I am happy that 
>it is so simple to use compared to treectrl. I would have a real 
>problem if treeview was not included in the final version of Tk.
>
>Also I think that the real way is somewhere in between treectrl and 
>treeview. The easy handling of treeview, together with  some more of 
>treectrl's features would be fine. But not all of treectrl's 
>features... what I'd appreciate is the functionality of treeview 
>plus:
>- putting arbitrary windows/widgets in tree columns, like in tktable 
>and treectrl
>- aligning text/labels/widgets in treeview (-sticky)
>- have editable text in tree columns
>
>I would be very happy with that, it's all I can imagine as necessary 
>for a tree widget in my (developer) life ;-).
>
>
>Eckhard


TreeCtrl was never meant to be a front-end widget, it was meant to be
a back-end that could be used to create front-end widgets. People have
been using the Canvas for years as a back-end for all sorts of listboxes
and tree widgets. More recently, Tablelist can be seen using the Text
widget as a back-end for a multi-column listbox. Neither the Canvas nor
the Text widget is particularly suitable for this purpose, especially
when a list grows large. How much easier it would be to implement a
BWidget or Tile tree or Tablelist listbox on top of TreeCtrl! That's what
TreeCtrl aims for, not to be a replacement for all those well-worn
widgets but to make it easier to implement them in the first place.

-- Tim Baker