From: Harald O. <Har...@El...> - 2009-08-07 07:30:28
|
Jeff Hobbs wrote: > I would not not create the modified BWidget "2.0" until you actually > have changes to implement. Don't strip out ttk support and call that > 2.0, as that seems pointless. If noone else steps up to support it that > is OK, but only create a new version if you plan to push it forward. > > We can live with BWidget 1.9 and TWidget 2.0. >> BWidget >> - Package name: BWidget >> - cvs: branch "BWidget" of module BWidget of tcl-lib >> - next release version: 2.0 >> - tcl/tk 8.2 or newer >> - no ttk support at all, will be removed Ok. The current support for ttk in BWidget is only useable the way "use what is senseful" but for example specifying a -bg somewhere leads mostly to error messages and undefined state. So the plan is: - do not use BWidget with ttk - no support here - plan to remove what is there (time frame: 1 year) - use TWidget with ttk (when it is there) About version numbers: 1.9 or 2.0 - I want to stay open here. No need to do things without reason but there should be a scope. If there is for example a new widget which has an implementation for BWidget and TWidget, I would not mind to develop BWidget and release a new version. Maybe, it might be senseful, to for example have the same widgets in a BWidget 2.2 and TWidget 2.2 release (same release number, same widget set). I don't know, we will see. Thank you, Harald |