I would like to have some informations about the
future versions of wxPython.
I find the actual state a little bit confusing. On one side,
there is the 2.4.0.7 version + a separate wx package. On the
other side, we have the 2.4.1.2 library and an updated
wx package.
It seems the new lib (2.4.1.2) has introduced some
"incompatibilities" against the 2.4.0.7 lib.
Will it not be better to "freeze" the wxPython lib,
and accelarate the "wx-new-style" transition, so
that users can update their old software?
I would like to have some informations about the
future versions of wxPython.
I find the actual state a little bit confusing. On one side,
there is the 2.4.0.7 version + a separate wx package. On the
other side, we have the 2.4.1.2 library and an updated
wx package.
It seems the new lib (2.4.1.2) has introduced some
"incompatibilities" against the 2.4.0.7 lib.
Will it not be better to "freeze" the wxPython lib,
and accelarate the "wx-new-style" transition, so
that users can update their old software?
Anyway, thanks for you great work.
PUtting together a formal roadmap is probably a good idea. I'll give it some thought over the weekend and see what I can do. I probably won't get anything on the website until after OSCON though.
In the meantime here are some tidbits: At this point in time the separate wx package should only be considered a technology preview. It is a usable sample of what I intend to do in the future, but it won't be official until there are reference docs being generated for it, and preferably until the new namespace is what is "native" and the wxPython.wx is what is "renamed." So it doesn't make sense to me to start porting the lib modules and such until then. If I can get all the ducks in a row then the switch will probably happen sometime in the 2.5.x (unstable api) series of releases.
ยทยทยท
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!