Hi,
I thought I could shed some light on the plans that I and the core dev
team have for the very near future of PySide. We're internally managing
the development using two-week Scrum sprints and just finished our
previous sprint (with great success, I might add), the results of which
have already been communicated to the list by the team members. The next
sprint starts today.
In the upcoming sprint, the biggest item is to have Qt object ownership
implemented in Shiboken. In addition to that, we'll be working on some
QUiLoader and generator improvements (bugs 77 and 98 in Bugzilla).
In the sprints after that, the current plan is to implement signals and
slots support in Shiboken, do some internal API work for Shiboken (if
necessary), and then port the different Qt modules to Shiboken. After
that (probably at some point in January), we should be able to replace
the current Boost.Python PySide implementation with the Shiboken one.
This will result in a fully API-compatible, but much smaller and more
portable PySide on which to base any future work.
Once the switch to Shiboken is complete, the next items to work on will
be the the new-style signals and slots and Python 3.x support. However,
it's still a bit early to give any precise estimates about their schedule.
Cheers,
ma.
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
