Comments on: UI Extensions for Mobile (Orbit) vs. Maemo 6 UI Framework

By: michael

michael — Wed, 17 Feb 2010 18:52:29 +0000

Re: email – I did that already, no reply yet …

By: zchydem

zchydem — Tue, 16 Feb 2010 10:18:20 +0000

@tackat You are right about the design and how it resembles the design of QStyle and QStyleOption!

I may have done some haisty conclusions there and I agree that this is a great opportunity to learn from these projects. You’re also right that you can develop widgets without knowing the existence of primitives and how they work. I also mentioned in the article, that that you can inherit the HbWidget and do all the things there, just like it works with QWidgets. (If I understood it correctly)

I’m still learning Qt, it’s a project that will never end. Thank you for your comments and patience:)

By: tackat

tackat — Tue, 16 Feb 2010 09:40:32 +0000

> You can easily see this problem from the diagram above
> and I’m quite surprised of this design.

Well, it mimics about almost exactly the design of QStyle, QStyleOption:

http://doc.trolltech.com/qq/qq13-styles.html

The only difference is that it takes QStyle to the next level by making the “primitives” / “controls” / “complex controls” QGraphicsItems and by making them accessible via the scene graph.

The great thing about the QStyle “MVC” pattern in Qt is that usually you don’t notice it as a programmer. And it doesn’t get in your way.

In Uiemo as well as in Maemo you don’t need to use the MVC pattern either in order to become productive. Both frameworks are exploring the capabilities of QGraphicsView and are helping (together with KDE’s Plasma) to make QGraphicsView even better. All of these projects have certainly QML and QWidgets-NG on their radar. And QML as well as QWidgets-NG are taking the lessons learned from these three projects. This is great because this will help the Qt universe to flourish further in the future.

By: dubik

dubik — Tue, 16 Feb 2010 07:29:46 +0000

Don’t get me wrong, I really want to see what you guys can do with itemsview-ng. It wasn’t very active for past few months and I thought you guys gave up. Glad to hear that you didn’t
I also like choice

By: zchydem

zchydem — Mon, 15 Feb 2010 17:53:13 +0000

@dubik & @mbm If I understand the codebase correctly widgets should be in: widgets-ng/src/gui/graphicswidgets/ ? There’re not so many widgets around yet, as dubik said, but it’s good to have challenges:)

By: mbm

mbm — Mon, 15 Feb 2010 17:03:33 +0000

@dubik I see no problem with having choice. There is also an advantage in being the second mover. It gives the opportunity to learn from previous efforts.

By: dubik

dubik — Mon, 15 Feb 2010 15:39:23 +0000

Are you still willing to finish it?
There are already many widgets around

By: zchydem

zchydem — Mon, 15 Feb 2010 11:12:41 +0000

@mbm Good point. I better get familiar with that source code. Thanks for the hint.

By: zchydem

zchydem — Mon, 15 Feb 2010 11:08:51 +0000

@michael you are right! I just had a lunch with chakie and we discussed with this problem and funny thing was that he faced this problem in 64 bits environment yesterday. There int has 64 bits and void pointer has 32 bits. When doing casting from void to int you will get an error. Definetly a critical issue when it comes to portability.

This is very good point to raise and maybe you can send an email to developer.feedback@nokia.com?

By: mbm

mbm — Mon, 15 Feb 2010 10:53:16 +0000

The widgets-ng code is available here: http://qt.gitorious.org/qt-labs/widgets-ng
We want this project to be done completely in the open, together with the rest of the open source community. So feel free to join us.