Hi Stephen,
I'm curious, why is sized_controls in this new top-level package of "wxaddons"? Considering the rest of the 'custom wxPython classes' are in wx.lib, wouldn't it make more sense to be there? Especially considering the fact that wxaddons isn't "versioned" like the rest of wx.
The original intention was that modules in wxaddons could be updated independently of wxPython, but still be included in the distribution. Modules in wx.lib, like 3rdparty modules and addons, are often worked on and updated independently of wxPython itself. Since they're tied to wxPython releases, though, users have to wait until the next wxPython release to get those improvements. (Which, in some cases, may mean waiting months.) So wxaddons was to be a sort of cheeseshop, where you could query modules and update them without requiring Robin to go through a whole wxPython release cycle each time. A separate repository was even created (http://wxpystonesoup.sf.net) for people to contribute wxPython modules to, and it had XML-RPC capabilities so that you could query modules, etc.
Unfortunately, no one seemed interested in being early adopters for this idea, and it's a lot of work to build nice interfaces and write lots of documentation when you're not sure anyone will even use the thing, so it's become a sort of failed experiment. I'm a bit perplexed as to why, though, as a number of people said they would want something like this; but when it was actually created, people still just continued to ask to get things put in wx.lib.
Regards,
Kevin
ยทยทยท
On Nov 29, 2007, at 2:13 PM, Stephen Hansen wrote:
--Stephen