|
From: Csaba N. <csa...@t-...> - 2006-11-22 21:17:10
|
Jeff Hobbs schrieb: > Will, > > Your points are in general correct, but overlook the direct remarks I > made below. Those features are certainly required for a decent dir > browser, but they are necessary for many other type of apps as well. > The lack of these in treeview is why people have turned to pure Tcl > alternatives even when treeview was available. If you want to look at > treeview as a multicolumn listbox, then it really fails in 2 areas - no > x scrolling and the inability to control stretch/shrink of columns. Joe > has said he likely won't have the time to address these before 8.5.0, > and thus I don't think it serves the core much to distract with the > treeview. > > Jeff > Jeff, While I generally agree with your criticism concerning the current development state of the treeview widget, I would have a quite serious problem if treeview wouldn't be integrated into the core. The reason is that in the tile-enabled version of Tablelist I make use of some treeview-related elements, like Treeheading.border and Treeheading.cell. Not having access to these elements would simply make it impossible for the Tablelist_tile package to work with Tk 8.5. Currently, Tablelist_tile is the only multi-column listbox with tile support, and a lot of people intend to keep using it with Tk 8.5. Also, your intention (decision?) to exclude treeview from the core doesn't take into account that there are quite a few people who already use treeview (in spite of its relatively early development state). After all, this wouldn't be the first widget in the core whose early versions are not yet quite satisfactory. With treectrl, the situation is different. This widget has always been a separate package, and from the programmer's point of view it makes no difference if it is merged into the core or not. Please, think about these arguments and don't exclude treeview from the core! Thanks, Csaba -- Csaba Nemethi http://www.nemethi.de mailto:csa...@t-... |