Hi Christian,
Last year, I started a porting of PySide to Qt5. I only worked on the QtCore module, but I succedded in having 99% of all classes and methods sucessfully wrapped. I made a quick python test with a custom class derived from QObject with signal/slot connections, and everything was working well. I didn't have time to continue with the QtGui porting since it's a huge task due the QtWidgets modules split. If you are interested, I can generate the patches and send them to you, especially the ones related to "tricky" qt metaobject stuff :) FYI, I used an old version of PySide (1.0.9), but hopefully there is not much difference with the current version (even if in this version, api-extractor was not yet merged with the shiboken module). IIRC, the main difficulties were: - replace Zc:wchar_t- with Zc:wchar_t to use the native type instead of ushort typedef (Qt5 is now compiled with wchar_t by default) - need explicit cast in qstring_convertsions: QString::fromUtf16(reinterpret_cast<const ushort*>(unicode) - headergenerator: need to order customized converter, due to dependencies: QString before QVariant before QStringRef, ... - replace deprecated macro qdoc with Q_QDOC (otherwise, the metaObject method is not seen) Cheers, Romain 2015-07-12 12:15 GMT+02:00 Christian Tismer <tis...@stackless.com>: > Thank you for the hint! > > Exactly this is what I saved for later, because I needed to gain more > experience by the porting, before going into this. > > cheers - Chris > > > On 12.07.15 09:50, redstone-cold wrote: > > I hope you guys be careful about the signal - slot mechanism in Qt5 > > http://www.riverbankcomputing.com/pipermail/pyqt/2014-January/033575.html > > > > 在2015年07月10 04时45分, "Christian Tismer"<tis...@stackless.com> > <tis...@stackless.com>写道: > > > Hi all, > > to let you be informed: > > PySide will live on. > -------------------- > > There is someone intensively working on porting PySide to Qt5, > with some help from Autodesk. > > I started end of May and am still very busy to get the most > important modules to compile. Now I think it is time to open > things up to the community and discuss some things, do reviews, > and most importantly: stop working alone for too long. > > This stuff is still under heavy development, and I'm inviting > experienced PySide developers to join me on the pyside-dev > list. I will post more details there. > > All the best - Chris > > -- > Christian Tismer :^) tis...@stackless.com > Software Consulting : http://www.stackless.com/ > Karl-Liebknecht-Str. 121 : http://www.pydica.net/ > 14482 Potsdam : GPG key -> 0xFB7BEE0E > phone +49 173 24 18 776 fax +49 (30) 700143-0023 > > > > > > -- > Christian Tismer :^) tis...@stackless.com > Software Consulting : http://www.stackless.com/ > Karl-Liebknecht-Str. 121 : http://www.pydica.net/ > 14482 Potsdam : GPG key -> 0xFB7BEE0E > phone +49 173 24 18 776 fax +49 (30) 700143-0023 > > > _______________________________________________ > PySide mailing list > PySide@qt-project.org > http://lists.qt-project.org/mailman/listinfo/pyside > >
_______________________________________________ PySide mailing list PySide@qt-project.org http://lists.qt-project.org/mailman/listinfo/pyside
