Dear Fathi, That was not my intention, well, in better- I meant heading to bind some new libs that did not exist when PyQt was created and thought of a couple of features that I will *personally* very much like in PySide once their finished, like this[0] one for example.
Sorry for mis-phrasing! Indeed, there are pros/cons to each and one should use the best tool for the job (tm) :-) Not to mention that PyQt is probably more spread and is heavily used all over since it has been around for longer. Thus could be easier to get going with since there are repository packages and tons of material to get started with both online and printed. This also shows promise to enable to port back and forth at relative ease[1]. [0] http://www.pyside.org/docs/pseps/psep-0102.html [1] http://stackoverflow.com/questions/1297660/pyside-vs-pyqt Fathi, please take liberty to make me stand corrected if I'm wrong and note my notes are just "in-my-experience" recommendations and should not be considered as authoritative advice. Cheers, Sivan On Mon, Jul 26, 2010 at 9:39 AM, <[email protected]> wrote: > Hi, > >> If you want the PySide bindings which are supposed to be a better, >> more complete version of the original Qt bindings, > > Please, don't spread FUD but give facts. > We have 2 competitors for the Python bindings. > Both have pros/cons and both try to push their implementation. > > I let the reader to search the relevant information to make his own choice. > > Cheers, > > Fathi > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
