For the record, it turns out that the build problem within PythonQt seems to be an issue with the pre-built Qt binaries for QOpenGL (at least on 4.6.1 and 4.6.2) - there's a mismatching signature for the method QGLFramebufferObject::blitFramebuffer(). This exists outside the context of PythonQt, and has also been mentioned here: http://old.nabble.com/Re:-Problem-with-snapshot-and-OpenGL-p27454323.html
If you've built Qt yourself, it appears this is not an issue. With this issue out of the way, PythonQt builds and works as advertised. I'd be very happy to see its dynamic binding functionality merged with PySide. Thanks to Florian for his patience with my questions as I investigated the problem :) Liam On Mar 19, 2010, at 2:13 PM, Florian Link wrote: > Hi, > > you should have a look at the trunk of the SVN repository of PythonQt, > which contains an almost finished PythonQt 2.0 with complete Qt > wrappers for Qt 4.6.1. I just did not have time to release it yet, but > it works quite well. > > PythonQt is very dynamic in its nature, like SMOKE and QtScript. > PythonQt 2.0 will offer (almost) complete Qt bindings via a wrapper > generator that is derived from QtScripts generator. In contrast to > PySide and PyQt, it generates additional QObject decorators, so it > uses the same dynamic mechanism for calling non-slots by generating > slots for them via the moc. > > Depending on your needs, PythonQt will probably do the job for you. > It works well to script your application via QObjects > signal/slots/properties and it supports the complete QtGui module. It > does not yet support deriving from QObjects in Python very well and it > does not yet support the new-style signals of PyQt4. > > By the way, I started writing the generator before PySide was > announced and after PySide became public, I already asked on this list > if a QtScript like API for PySide would be interesting, but nobody > jumped on it... > > In the long run, I consider modifying PythonQt to either use PySide or > SMOKE for generation of the wrappers, while still providing the > QtScript-like API for integration into Qt C++ Applications (which is > the focus of PythonQt). > My idea would be to merge the dynamic dispatch of PythonQt and static > wrapping of PySide into one by extending PySide with dispatchers that > are called when there is not static knowledge on an object... > > regards, > Florian Link > _______________________________________________ > PySide mailing list > [email protected] > http://lists.openbossa.org/listinfo/pyside
_______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
