Linked by Hadrien Grasland on Tue 11th Jan 2011 13:40 UTC
Graphics, User Interfaces Nowadays smartphones, tablets and desktop/laptop computers are all siblings. They use the same UI paradigms and follow the same idea of a programmable and flexible machine that's available to everyone. Only their hardware feature set and form factor differentiate them from each other. In this context, does it still make sense to consider them as separate devices as far as software development is concerned? Wouldn't it be a much better idea to consider them as multiple variations of the same concept, and release a unified software platform which spreads across all of them? This article aims at describing what has been done in this area already, and what's left to do.
Thread beginning with comment 456984
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: umm
by Neolander on Tue 11th Jan 2011 15:55 UTC in reply to "RE[4]: umm"
Neolander
Member since:
2010-03-08

Qt Quick is Qt Quick, Qt Stylesheets is Qt Stylesheets. One is largely inspired by CSS, the other is applications.

I.e., you have confounded those two technologies ;)

As I said, I've yet to find a good introduction to the subject to clear up my vision of it. What I'm looking for is something written by a QT developer or enthusiast which explains in a few paragraphs, without going in technicalities...

* What's the point of those new QT technologies, what Nokia designed them for.
* Why I should use them as a developer, what they bring on the table, how they solve the problem which they were designed to solve.

If you have some links which do exactly that, please share them !

Edited 2011-01-11 15:56 UTC

Reply Parent Score: 1

RE[6]: umm
by vivainio on Tue 11th Jan 2011 20:12 in reply to "RE[5]: umm"
vivainio Member since:
2008-12-26

What's the point of those new QT technologies, what Nokia designed them for.


- Easier coding of "nice" user interfaces with free-form animations. You can translate "designer" angle quite directly to code ("this button is right of this image, at the bottom of the view")

- Need for speed. Unless you get great framerate (preferable the magical 60fps) on a phone these days, you fail to attract users. Most of iPhone attraction comes from framerate, users just don't know it ;-).

Future (internal) Nokia UI innovation will all happen on top of QML, for a good reason. It's also gathering momentum outside Nokia, e.g. KDE community.

QML is also the *only* UI technology we fully support for external developers in coming devices (both MeeGo and Symbian). Unless you count OpenGL, but that is targeted at an entirely difference class of programmers (3d games).
Why I should use them as a developer, what they bring on the table, how they solve the problem which they were designed to solve.


If you are a desktop application developer, old style QWidgets are the easiest way forward for now. Desktop applications don't need to be too flashy, and usage paradigm is always quite predictable.

How:

- Declarative programming style endorsed (property binding, anchors)

- Only support features that can be made fast on GPU. Complex stuff composed with these fast elementary features

- Nice syntax

Reply Parent Score: 4

RE[7]: umm
by Neolander on Tue 11th Jan 2011 20:19 in reply to "RE[6]: umm"
Neolander Member since:
2010-03-08

Thank you very much for the explanation ! ;)

Reply Parent Score: 1

RE[7]: umm
by shmerl on Wed 12th Jan 2011 04:00 in reply to "RE[6]: umm"
shmerl Member since:
2010-06-08

What about GTK+ on Meego? It's supposed to be supported too.

Reply Parent Score: 1

RE[6]: umm
by vivainio on Tue 11th Jan 2011 20:21 in reply to "RE[5]: umm"
vivainio Member since:
2008-12-26
RE[7]: umm
by Neolander on Tue 11th Jan 2011 21:08 in reply to "RE[6]: umm"
Neolander Member since:
2010-03-08

Well, I recently got some flash plugin issue which makes every sound coming from it horribly painful to hear (32kbps MP3 is what comes to my mind), so I can't listen to all of this at the moment, but arriving at 17 minutes (when he's done with his Edit example and starts to move on to another interface components), I think I get the overall idea.

As I learned programming with Delphi, I still feel a bit nostalgic about its GUI UI designer, but I must admit that this looks indeed as fun as a text-based UI design tool can get. Also, love the auto-completion features of QT Creator.

On the other hand, you also confirmed to me that this likely won't solve the problem which I'm talking about in this article, despite what lemur2 was implying. You can write UIs for various devices using this same tool right, but if I'm not misunderstood you still have to design UIs on a per-device basis.

Edited 2011-01-11 21:23 UTC

Reply Parent Score: 1