On Sun, Feb 5, 2012 at 8:29 PM, <[email protected]> wrote:

>  Currently, ‘QT += declarative’ adds the headers and library for the
> declarative UI engine, while ‘QT += quick’ adds the headers and library for
> the Qt Quick 2 QML components.  An application may choose to use the
> declarative engine without the bundled components.  In the first version of
> Qt Quick, both aspects were bundled together into a single library, which
> is now present in Qt 5 as the ‘quick1’ module.
>
****
>
> ** **
>
> The plan is to have these both available in Qt  5 as independent modules.
> For this, we need to have different module names, and symbol names that do
> not clash.  I will rename all the classes currently named ‘QDeclarative…’
> in the qtdeclarative module to ‘Qml…’ or ‘QQuick…’ as appropriate.  This is
> slightly held up by the fact that we would like a small change to moc to
> preserve backward compatibility.
>

I see. That separation would be nice; I thought QtQuick2 would also bundle
engine and components in the same module. However, I think the
'declarative' module name is misleading when used for QtQuick2 because all
class prefixes in this new module won't be 'QDeclarative*' anymore and also
because it doesn't highlight that this module just contains the engine.
Maybe something like 'QT += quickcore quickcomponents' would be more clear.
For QtQuick1, on the other hand, 'declarative' has some meaning due
historical reasons and the API itself, but 'quick1'  would also be a good
module name.

Regarding the 'Qml*' prefix option; I would vote against it, since it
doesn't follow the Qt name standards. AFAIK, the 'Q' prefix should be
present in all classes followed by the class name in camel-case. As QML is
an acronym for itself, it should have a Q prefix as well, like 'QXml*',
'QDom*' and others. But I would vote for the 'QQuick*' prefix instead,
since it's already being used in the rest of the API.

Br,
Adriano
_______________________________________________
Qt-qml mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt-qml

Reply via email to