Slashdot Mirror

I've done quite a bit of code but I fully admit to being a lightweight at GUI development. Having said that, QML makes the design of the interface pretty easy... even including wacky animations & stuff. Here's a link to some Python based QML tutorials: http://www.pyside.org/docs/pyside/tutorials/index.html

What options does this leave for Qt-based development on embedded platforms?

Maemo on the N900 felt like the right direction with Nokia backing Qt, especially with projects like PySide created soley to offer a LGPL-licensed Python wrapper available to commercial developers (as opposed to PyQt). This permitted a single codebase to target desktop and mobile/tablet environments using a pleasant and completely open toolchain. MeeGo was set to carry on with Qt/X11.

But according to MeeGo's updated website, "We believe the future belongs to HTML5-based applications, outside of a relatively small percentage of apps, and we are firmly convinced that our investment needs to shift toward HTML5."

There are other ways than rewriting the same thing several times. You don't even have to use C or C++. You already need at least different layouts for desktops, tablets (really just desktops without the input devices), and phones (or: tiny screen devices) for an application to be usable. So what is the advantage of using an overgrown design-by-committee hack that has repeatedly rejected all innovation in the name of compatibility? It doesn't help that HTML5 is probably more difficult to implement than the entire rest of an operating system.

Having used everything on the list and much more (such as wx, GTK, etc), as well as making my own toolkits for embedded devices and products, my personal experience tells me hands down that Qt is the best choice for anything GUI related. It's power, ease of use, tools, documentation and learning curve are unparalleled to this day and age. Any other toolkit or API I've use fails in one or more of such areas.
Qt is the only toolkit that made me feel as if they could know in advance everything i'd ever need (so when i go to the docs it's there, right how as i imagined it should be), yet keeping the bloat down with great modularization. I have used it from C++ as well as from Python with great success.

Nokia has developed a LGPL python binding to QT since the existing pyQT is not fully open. Why should they do that if they don't count on Python? http://www.pyside.org/

If you're interested in using Qt with Python you should take a look at PySide which is being developed by Nokia.

You will probably want PySide since it gives all Qt functions to Python and was written with mobile devices in mind. It is not "done" yet but there is just enough for you to get your hands dirty with.

Worth noting that PyQt4 is still GPL (not LGPL, like Qt4), which can make a difference for proprietary software. There's a mostly-PyQt-compatible PySide if you need LGPL (or if you prefer an "official" binding), but it's still in 0.x stage.

It was already open-source, just under a different license.

It also looks like PySide is nearly 100% compatible with PyQt, which decreases the headache people who want to switch.