[wxPython-dev] 2.8.7.0 coming soon

[Robin Dunn]

Andrea Gavana wrote:
> Hi Robin & All,
> 
>     I remember we spoke some time ago about FlatMenu, LabelBook and
> the other goodies for a possible inclusion in wx.lib (?), but in the
> end we didn't get to a definitive answer, What should I do? Is it
> better to wait? Or is it better for those widgets to stay where they
> are right now?

If you have time in the next few days then go for it.  Otherwise it will 
probably need to wait for the next release.

There is also the question of where to put them, and it might be a good 
idea to get feedback from the others in this group about it.  First a 
little background for everybody else:  I've recently opened up a new 
place in the SVN for 3rd Party things to make it a little easier for 
people to maintain their own contributions, see 
https://svn.wxwidgets.org/svn/wx/wxPython/3rdParty/.  So far we have 
XRCed and Editra there.  Each developer gets a folder at that location 
and then I'll use svn:externals to map that folder into the main 
wxPython trees for each active branch of development.  This allows the 
contributing developers to only need to maintain their code in one place 
instead of needing to make their changes in more than one wxPython 
branch.  All they have to do is make their changes in the one place and 
make sure their code is compatible with the active wxPython branches. 
(Just 2.8 at the moment, but I'll be shifting focus to 2.9 soon.)

I've been thinking about moving Andrea's modules to the 3rdParty spot so 
he can get the same benefits, but because of a limitation of 
svn:externals it only works with folders, not individual files.  So that 
means that his modules would need to be moved to a Python sub-package 
instead of being located directly in the wx.lib package.  It wouldn't be 
hard to migrate to that structure, it would simply need some stub 
modules in wx.lib that import from the package, but I have no idea what 
to name that sub-package.  I would prefer to have the name be something 
about the functional grouping of modules instead of just something like 
wx.lib.andrea or wx.lib.ag, but nothing comes to mind.  Anybody have any 
better ideas?

P.S.  Chris B., this would also be a good way to manage getting updates 
of FloatCanvas into wxPython releases!  Once it is set up it would 
require almost zero effort on your part.  (hint! hint!)

-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!