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.
Permalink for comment 457034
To read all comments associated with this story, please click here.
RE[6]: umm
by vivainio on Tue 11th Jan 2011 20:12 UTC in reply to "RE[5]: umm"
Member since:

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.


- 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