Open sebastianelsner opened 9 years ago
I'm not sure pyside will be actively developed in the future. Qt support ends at 4.8 and I heard that qt guys would more likely rely on pyqt... (though I might be wrong on this :)) For the rest, I don't see clearly how pyqode would help us in supporting pyqt4/5 ? Do you means using the linters to check for code compliance in the sources ?
If there is no sponsor in the future for PySide, it will die, you are right. We use PyQt for all we do right now, but using PySide in Maya/Nuke/Houdini is quite convenient, since its bundled and compiling PyQt for each product X compiler X OS is very painful. If we wanted to use any widget of PuliMonitor (like the job view) in any of those programs (which would be quite nifty!) pyqode would provide an abstraction layer. Also with PyQt5 it provides an abstraction because there lots of classes were moved to different submodules (e.g. all widgets were moved to QWidget package instead of QtGui). So we could make this work out of the box for people using cutting edge desktops, which are on Qt5 without requireing Qt4 and still run any widget in a host programm like Maya.
I think it would be interesting to ass support for the bindings mentioned in the titles. This would allow easy sharing of code, ease portability to newer systems/qt versions and possibly enable embedding puli widgets in maya/houdini/nuke interface without the trouble of building pyqt for each host app (since pyside is now embedded in most). https://pypi.python.org/pypi/pyqode.qt looks very interesting