OSNews

I added the Qt info, just because I wanted to add the information as to what they used before. Readers here know what is what so they would be able to make the distinction between a toolkit and a language. I wanted to add the info because Mizi was keep bitching about Qt in the past that it's too slow and not flexible enough and that they wanted to move away from it.

"I wanted to add the info because Mizi was keep bitching about Qt in the past that it's too slow and not flexible enough and that they wanted to move away from it."

So did they create their own UI toolkit for Python or what?

I wanted to add the info because Mizi was keep bitching about Qt in the past that it's too slow and not flexible enough and that they wanted to move away from it.

OK. So let's get some insight into that, quoted above:

"Qt has some advantages. It is good at multimedia support. But we are building own own GUI toolkit that will run on X Windows."

So let me get this right. They're rolling their own toolkit, on top of X windows(!) and they're doing it in Python - and they expect this to be faster, and more flexible?! They also still think that Qt is good for multimedia.

Mizi hopes a new slimmed-down GUI will help its stack support single-core mobile phone designs in the future, it says.

That's a highly flimsy reason for coming up with what will be a complex piece of software, in house. Sounds like technology wanking to me. Coming up with and maintaining your own toolkit is not to be entered into lightly, and I'm not too sure why they're not just bypassing X windows and using framebuffer as Qtopia does.

Edited 2007-05-18 19:05

seems they indeed are trying to get rid from Qt, I did see this in the Prizm 2.5 announcement:

Prizm's 2.5's graphics stack is based on TinyX, along with a Qt GUI toolkit. However, the company plans to move to an in-house GUI toolkit for a future Prizm release. Lee explains, "Qt has some advantages. It is good at multimedia support. But we are building own own GUI toolkit that will run on X Windows."

Mizi hopes a new slimmed-down GUI will help its stack support single-core mobile phone designs in the future, it says. Other features under development include customization tools and documentation for solution partners, and "network convergence" features, including WiFi support. Lee says he expects to demonstrate an "interim version" of Prizm 3.0 during Q3 of 2006.

How well do the pyQT bindings stack up to the pygtk bindings?

I'm not sure about pyGTK since I haven't used it, but pyQt is very complete. Probably the best language binding for Qt. On par with the officially supported C++ and Java.

I don't think going to Python + GTK from C++/Qt would get you any benefits. Certainly not execution speed. I would guess that they wrote their own lightweight toolkit. Kinda makes sense anyway. Why they didn't use Qtopia or a homebrew thing in the first place is beyond me.

Python and "some mysterious toolkit"... It is probably gtk.

I doubt it, because they'd just be trading one set of problems for another. They're still using X windows for heavens' sake. It does seem from their announcement that they're doing their own internal toolkit with some sort of Eclipse based framework.

GTK seems to be fairly popular in the embedded/mobile space.

Sorry, but it isn't. Very, very, very few embedded or mobile devices use GTK and I don't see any device running it in any mobile shop I've seen. It also has some pretty fundamental performance issues that need to be solved. Qt is pretty scarce as well, but many devices sold in the Far East use it quite a bit.

How well do the pyQT bindings stack up to the pygtk bindings?

PyQt is exceptionally complete, and has been for some time. When you've got PyQt available there's no way you'd want to drop it for PyQTK, but their reasons for doing what they're doing seem to be muddled at best.

This is why they got rid of Qt Embedded. The A780 uses Qt Embedded, just like the old version of Mizi.