Hi Florian - thanks for your message. I was actually just playing with PythonQt trunk, but it doesn't want to build on OS X from a fresh checkout. The only build instructions say "qmake && make all", but the link is failing at the moment:
Undefined symbols: "QGLFramebufferObject::blitFramebuffer(QGLFramebufferObject*, QRect const&, QGLFramebufferObject*, QRect const&, unsigned int, unsigned int)", referenced from: PythonQtWrapper_QGLFramebufferObject::static_QGLFramebufferObject_blitFramebuffer(QGLFramebufferObject*, QRect const&, QGLFramebufferObject*, QRect const&, unsigned int, unsigned int)in com_trolltech_qt_opengl0.o That may be just a temporary issue on trunk of course, but it makes it a little tough to evaluate the system for our needs :) One other issue is that on the documentation front page (http://pythonqt.sourceforge.net) it says it's compatible with up to Python 2.6, but in build/python.prf in the source, Python 2.5 is the highest version provided as an example of possible values. Again, 2.6 may work but it's difficult to know without a very thorough investigation. Thanks for any tips that might help us get started a little more easily! 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
