Re: [Tile-dev] Tree widget API

[Bryan O. <br...@bi...>]

Jeff Hobbs wrote:

 > Bryan Oakley wrote:
>>I think what I'd like is to see tktreectrl in the core but hidden (or 
>>maybe not...). We could then graft some APIs on top so that it can be 
>>treated as several different widgets. At the very least there would be a 
>>tree API and another API for the listbox-like features 
>>(showing rows and columns of icons or text).
> 
> 
> Someone just mentioned this point on the tile-dev list again,
> with reference to your earlier clt comments.

I'll keep planting the seed until something sprouts :-)

To make this work we'd need to modify tktreectrl to take a -class 
option, so the API layer could do something like "tktreectrl -class Tree 
..." to create the actual widget. Then it wouldn't take much more than 
an "interp alias {} tree {} tktreectrl -class Tree" and we're off to the 
races. Of course, we'd have to tweak the bindings or bindtags, etc...

With that, the bulk of the work would be in writing man pages broken up 
by class, and only documenting the options that make sense in a 
particular context.