Re: [Tcllib-devel] TBWidget Branch (please help on cvs organisation)

[Damon C. <da...@tc...>]

> FWIW we (at ActiveState) have largely dropped BWidget in favor of the
> tklib widget package (which I'm the primary author for) that is snit
> (snidget) based, along with using newer core widgets.
>
> I do wonder the efficacy of a pure ttk TWidget ... done "right", it
> would remove a lot of BWidget cruft and look like tklib/widget.  Of
> course you can just make it 100% BWidget compatible, but that seems to
> be what BWidget 1.9 already is.

BWidget is a fine package, but the underlying structure of the widgets  
is not very nice to program in.  In fact, it's quite a pain in the  
ass.  BWidget 1.9 is a fine, final release of the package.  Call it  
what it is and let's move on to something else.

There are things in BWidget worth saving, but I think we're better off  
taking what is good, moving it into a package like tklib/widget and  
then building on that.  There's a lot of cruft in BWidget that simply  
can't be gotten rid of if you want to maintain any sort of backward  
compatibility.  I don't think that should be our goal.

Which is not to say that the widget-level APIs should change just for  
the sake of change, but I don't think we should include every widget  
currently in the BWidget toolkit in some new toolkit.  Some of the  
widgets are just plain stupid, and several others are completely  
unnecessary.

What does tklib/widget currently support that is basically ripped from  
BWidget?  What widgets from BWidget are actually worth saving?

D