RE: [Tile-dev] Tree widget API

[Jeff H. <je...@Ac...>]

> > It's only fault is the complexity of the API.  Is this unavoidable due 
> > to the complexity of the widget, or is this something that post-dev 
> > experience and more use with the widget can help to rationalize?
> 
>     I'm playing with it now to try and answer some of those 
> questions, but someone else with more experience with the 
> widget might be able to better answer them.  You seem to have 
> worked with it a little, Jeff. 
> Any initial musings you'd like to share?

> PS:
> treectrl.n     108k

text.n:    78K
canvas.n:  73K
tktable.n: 60K.

Are those hard to understand?  Well, for some, but eventually
you work through it all.  I think at least the treectrl docs
are mostly complete, even if a few more samples might help
explain things.

As for initial impressions, it has some elements of the canvas
without using the same naming conventions.  It gets a bit
blurry if you add tile with its new naming conventions into
the mix, as treectrl has "elements" and "styles".  It's kind
of Tix like in some respects.  Tim may be the best person to
answer that.

Jeff