On 6/22/11 3:03 AM, "Alan Alpert" <alan.alp...@nokia.com> wrote:
>Qt Declarative is in there as "A QML Engine Module", which presumably >includes >the basic set of primitives in the QtQuick import as well as the engine >itself. That's the entire QtDeclarative module right there (except for >labs >modules, which we can all agree are not essentials). Right. >I don't know why it wasn't just called "QtDeclarative" though. Perhaps >because >there are to be a growing number of declarative add-ons, and so the >engine >module is no longer Qt's whole declarative offering? The reason is that I tried to be consistent with Lars's Qt5 white paper, that talks about a QtDeclarative module that links against QtWidgets and provides the existing Graphics View based classes. In that case, there would be a new name for the scene graph based QML engine module. By the way, with the proposed naming, the QWidget related modules would be called QtAddOnDeclarative, QtAddOnWidgets etc.. Best regards, Henry _______________________________________________ Opengov mailing list Opengov@qt-labs.org http://lists.qt-labs.org/listinfo/opengov
