[Development] Qml what for, was Platform Content Selection

Attila Csipa qt at csipa.in.rs
Tue Jan 15 14:34:57 CET 2013


On 15/01/13 12:22, Mohamed Fawzi wrote:
>
>> - Which real world problems do we address? [By "real world" I
>>    explicitly do include handset makers, and potential single-
>>    platform interest in that area, but it's definitely not
>>    restricted to those]
> Dynamic interfaces, with transitions and generally lot of dynamic layout.
> This is relevant especially for touch devices.

I think the short answer would be just "the JavaFX Script (a.k.a. F3) 
inspired .ui equivalent for the Qt5 era". Gives you the dynamic parts, 
fast iteration, modularity, cleaner syntax, etc. That said, QML *is* a 
language, and there is nothing (non) cross-platform about it, it really 
depends what lies underneath it. We have various QtQuick 
implementations, then there is cascades, various platform (Symbian, 
MeeGo) components... It's the *approach*, the base syntax that is 
platform-agnostic, not the particular APIs or source code (which is what 
most people seem to misunderstand as cross-platform is often used in 
different contexts outside of the Qt world).

Attila



More information about the Development mailing list