aboutsummaryrefslogtreecommitdiffstats
path: root/src/declarative/designer/designersupport.h
Commit message (Collapse)AuthorAgeFilesLines
* Say hello to QtQuick moduleKent Hansen2011-12-021-153/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change moves the QtQuick 2 types and C++ API (including SceneGraph) to a new module (AKA library), QtQuick. 99% of this change is moving files from src/declarative to src/quick, and from tests/auto/declarative to tests/auto/qtquick2. The loading of QtQuick 2 ("import QtQuick 2.0") is now delegated to a plugin, src/imports/qtquick2, just like it's done for QtQuick 1. All tools, examples, and tests that use QtQuick C++ API have gotten "QT += quick" or "QT += quick-private" added to their .pro file. A few additional internal QtDeclarative classes had to be exported (via Q_DECLARATIVE_PRIVATE_EXPORT) since they're needed by the QtQuick 2 implementation. The old header locations (e.g. QtDeclarative/qquickitem.h) will still be supported for some time, but will produce compile-time warnings. (To avoid the QtQuick implementation using the compatibility headers (since QtDeclarative's includepath comes first), a few include statements were modified, e.g. from "#include <qsgnode.h>" to "#include <QtQuick/qsgnode.h>".) There's a change in qtbase that automatically adds QtQuick to the module list if QtDeclarative is used. Together with the compatibility headers, this should help reduce the migration pain for existing projects. In theory, simply getting an existing QtDeclarative-based project to compile and link shouldn't require any changes for now -- but porting to the new scheme is of course recommended, and will eventually become mandatory. Task-number: QTBUG-22889 Reviewed-by: Lars Knoll <lars.knoll@nokia.com> Change-Id: Ia52be9373172ba2f37e7623231ecb060316c96a7 Reviewed-by: Kent Hansen <kent.hansen@nokia.com> Reviewed-by: Sergio Ahumada <sergio.ahumada@nokia.com>
* Add QT_BEGIN_HEADER/QT_END_HEADER macrosSergio Ahumada2011-10-251-0/+4
| | | | | | | | | Fixing `macros' function test of `tst_headers' Task-number: QTQAINFRA-324 Change-Id: I0cd3ea6ee631c3e19078eda2104c78803d77939d Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com> Reviewed-by: Charles Yin <charles.yin@nokia.com>
* Rename Qt Quick-specific classes to QQuick*Kent Hansen2011-10-211-25/+25
| | | | | | | | | | | | | | | | | | | | | | The QSG (SceneGraph) prefix is too generic for Qt Quick(2)-specific classes. All the classes and files in the declarative/items directory have been renamed. In particular, for classes that are currently public, the renaming is as follows: QSGView --> QQuickView QSGCanvas --> QQuickCanvas QSGItem --> QQuickItem QSGPaintedItem --> QQuickPaintedItem The header files have been renamed accordingly (e.g. qsgview.h --> qquickview.h). Change-Id: Iac937fff81db20bb639486a793c3aeb5230b038c Reviewed-by: Kent Hansen <kent.hansen@nokia.com>
* Fix missing and outdated license headers.Jason McDonald2011-09-091-18/+17
| | | | | | Change-Id: I940ced2e84a86daabc5158d348b05b7532cb1c22 Reviewed-on: http://codereview.qt-project.org/4314 Reviewed-by: Alan Alpert <alan.alpert@nokia.com>
* Add bounding rectangle for rendering images in designer supportMarco Bubke2011-08-311-1/+2
| | | | | | | | | | Elements can be outside the root items bounding rectange. So we compute the bounding rectangle of an item and its children on the designer side. We exclude all children which are the designer created. Change-Id: I3c4f9ca5291c8f65e3670be1fd0900edf449b46f Reviewed-on: http://codereview.qt.nokia.com/3963 Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>
* Add an abstraction layer for the qml designerMarco Bubke2011-08-311-0/+149
The Qml Designer for Qt4 is using private headers but this broke very often because nobody outside of the designer team was aware of it. This is an attempt to define a clear interface which the designer is using. Change-Id: I9ad2db234043da8e787024d3c2d346356bbbef47 Reviewed-on: http://codereview.qt.nokia.com/3608 Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com> Reviewed-by: Aaron Kennedy <aaron.kennedy@nokia.com>