1. 27 Feb, 2012 1 commit
    • Matthew Vogt's avatar
      Create a forwarding declarative module. · 377eb94e
      Matthew Vogt authored
      The declarative module has been replaced by the qml module.  To allow
      existing projects which depend on the old declarative module to build,
      add a new declarative module which forwards dependencies on to the
      new qml module.
      This module contains only redefinitions of old symbol names to their
      new replacements, and creates forwarding headers that include the
      replacement headers provided by the qml module.
      This is a temporary change to prevent breaking existing projects
      that depend on the declarative module. After clients have had an
      opportunity to update their code to the use the new interfaces,
      it can be removed.
      Task-number: QTBUG-23737
      Change-Id: I3cec5ceec4f9725c258e3672360a05ea87d3ca2f
      Reviewed-by: default avatarMartin Jones <martin.jones@nokia.com>
  2. 24 Feb, 2012 1 commit
  3. 02 Feb, 2012 1 commit
  4. 02 Dec, 2011 1 commit
    • Kent Hansen's avatar
      Say hello to QtQuick module · 6c8378ea
      Kent Hansen authored
      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
      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
      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: default avatarLars Knoll <lars.knoll@nokia.com>
      Change-Id: Ia52be9373172ba2f37e7623231ecb060316c96a7
      Reviewed-by: default avatarKent Hansen <kent.hansen@nokia.com>
      Reviewed-by: default avatarSergio Ahumada <sergio.ahumada@nokia.com>
  5. 07 Oct, 2011 1 commit
  6. 01 Sep, 2011 1 commit
  7. 31 Aug, 2011 1 commit
  8. 29 Jul, 2011 1 commit
  9. 12 Jul, 2011 1 commit
  10. 20 May, 2011 1 commit
  11. 13 May, 2011 2 commits
  12. 02 May, 2011 1 commit
  13. 29 Apr, 2011 1 commit
  14. 27 Apr, 2011 7 commits