Sorry to ask a really dumb question, but I just spent a solid half
hour failing to find out.
What is the difference between packages in wx.lib and in wx? It seems
like the stuff in wx.lib is sometimes a little more out there and/or
unstable, but that doesn't seem to be a general rule... It's driving
me crazy. Please help 
oolee wrote:
Sorry to ask a really dumb question, but I just spent a solid half
hour failing to find out.
What is the difference between packages in wx.lib and in wx? It seems
like the stuff in wx.lib is sometimes a little more out there and/or
unstable, but that doesn't seem to be a general rule... It's driving
me crazy. Please help
They're third-party additions to wxPython that may not be in the
original wxWidgets code. They're also generally
user-contributed/maintained and offer generic alternatives to the
official wx classes.
e.g. wx.lib.buttons provides generic buttons that look the same across
all OS' as they don't draw the buttons using the native renderer
···
--
Steven Sproat, BSc
Ahhh, thanks that makes sense. So I guess in general it doesn't
make that much sense to report a bug in a wx.lib package, unless
I know who maintains it? Or is there a system to route the tickets
to the right person...
···
On Aug 7, 7:15 am, Steven Sproat <spro...@gmail.com> wrote:
oolee wrote:
> Sorry to ask a really dumb question, but I just spent a solid half
> hour failing to find out.
> What is the difference between packages in wx.lib and in wx? It seems
> like the stuff in wx.lib is sometimes a little more out there and/or
> unstable, but that doesn't seem to be a general rule... It's driving
> me crazy. Please helpSteven Sproat wrote:
They're third-party additions to wxPython that may not be in the
original wxWidgets code. They're also generally
user-contributed/maintained and offer generic alternatives to the
official wx classes.e.g. wx.lib.buttons provides generic buttons that look the same across
all OS' as they don't draw the buttons using the native renderer
oolee wrote:
···
On Aug 7, 7:15 am, Steven Sproat <spro...@gmail.com> wrote:
oolee wrote:
Sorry to ask a really dumb question, but I just spent a solid half
hour failing to find out.
What is the difference between packages in wx.lib and in wx? It seems
like the stuff in wx.lib is sometimes a little more out there and/or
unstable, but that doesn't seem to be a general rule... It's driving
me crazy. Please help
Steven Sproat wrote:
They're third-party additions to wxPython that may not be in the
original wxWidgets code. They're also generally
user-contributed/maintained and offer generic alternatives to the
official wx classes.e.g. wx.lib.buttons provides generic buttons that look the same across
all OS' as they don't draw the buttons using the native renderer
Ahhh, thanks that makes sense. So I guess in general it doesn't
make that much sense to report a bug in a wx.lib package, unless
I know who maintains it? Or is there a system to route the tickets
to the right person...
Sorry, I was a little wrong in that regard - not all the original
authors now maintain the libraries, but any bugs reported are generally
looked at and fixed. If you could provide a patch then that's also
beneficial.
You can report bugs at http://trac.wxwidgets.org/
see: wxTrac has been migrated to GitHub Issues - wxWidgets
--
Steven Sproat, BSc
Another way to look at it is that the things in the wx package are mostly wrapped C++ classes, while everything else is pure Python code.
···
On 8/7/10 5:15 AM, Steven Sproat wrote:
oolee wrote:
Sorry to ask a really dumb question, but I just spent a solid half
hour failing to find out.
What is the difference between packages in wx.lib and in wx? It seems
like the stuff in wx.lib is sometimes a little more out there and/or
unstable, but that doesn't seem to be a general rule... It's driving
me crazy. Please helpThey're third-party additions to wxPython that may not be in the
original wxWidgets code. They're also generally
user-contributed/maintained and offer generic alternatives to the
official wx classes.
--
Robin Dunn
Software Craftsman