1. 15 Apr, 2011 1 commit
  2. 14 Apr, 2011 1 commit
  3. 13 Apr, 2011 2 commits
    • hjk's avatar
      Update license. · 83976639
      hjk authored
      83976639
    • dt's avatar
      Fix qt version number in Qt Quick Wizard · d0f7be18
      dt authored
      Temporal lapse in understanding which qt version is required for the Qt
      Quick Wizard. On Maemo we have the Qt Quick compat plugin which allows
      the generated project to work with 4.7.0. In theory that doesn't apply
      to symbian, but qt 4.7.0 does not support symbian. (And on the desktop
      everyone has upgraded.)
      
      Reviewed-By: ck
      d0f7be18
  4. 12 Apr, 2011 1 commit
  5. 07 Apr, 2011 1 commit
  6. 04 Apr, 2011 2 commits
  7. 30 Mar, 2011 1 commit
  8. 21 Mar, 2011 2 commits
  9. 18 Mar, 2011 4 commits
  10. 17 Mar, 2011 1 commit
  11. 16 Mar, 2011 3 commits
  12. 02 Mar, 2011 1 commit
  13. 28 Feb, 2011 1 commit
  14. 25 Feb, 2011 1 commit
  15. 22 Feb, 2011 2 commits
    • Thorbjørn Lindeijer's avatar
      Specify the right parent for the QDeclarativeViewObserver · 3383a204
      Thorbjørn Lindeijer authored
      This makes sure it gets deleted together with the QmlApplicationViewer,
      rather than probably not at all when no parent is specified for the
      viewer (which is the default).
      
      Reviewed-by: Alessandro Portale
      Reviewed-by: Christiaan Janssen
      3383a204
    • dt's avatar
      Qt4ProjectManager: New TargetSetupPage · 06ee3aee
      dt authored
      Rewrite the target setup page to look and baheve better.
      Noteable better at:
      - Disabling shadow building
      - Deselecting whole targets
      - Adding import directories
      
      Api-wise, Targets derived from Qt4BaseTarget have two ways to customize
      the targetsetuppage.
      
      a) Reimplement availableBuildConfigurations
      b) Leave createTargetSetupWidget and create(... Qt4TargetSetupWidget)
         in their default implementation. (Or only slightly customize like
         the desktop target does.)
      
      Or:
      a) Make a dummy implementation for availableBuildConfiguration
      b) Replace createTargetSetupWidget and return your own widget
         (It should match the look and feel from the other widgets.)
         It needs to be derived from Qt4TargetSetupWidget
      c) Also replace the create create(... Qt4TargetSetupWidget) function
         and set up the target anyway you want.
      06ee3aee
  16. 16 Feb, 2011 1 commit
  17. 15 Feb, 2011 2 commits
  18. 11 Feb, 2011 1 commit
  19. 10 Feb, 2011 1 commit
  20. 09 Feb, 2011 3 commits
  21. 07 Feb, 2011 2 commits
  22. 06 Feb, 2011 3 commits
  23. 04 Feb, 2011 1 commit
  24. 03 Feb, 2011 2 commits
    • Alessandro Portale's avatar
      Refactoring the template code updater. Reusable for html5 · efc59617
      Alessandro Portale authored
      Less static functions, more ploymorphism.
      efc59617
    • Alessandro Portale's avatar
      Removing the usage of Avkon to lock the screen orientation · d4e58902
      Alessandro Portale authored
      Locking the screen orientation was not a Qt feature of the Symbian
      port till Qt 4.7.2. Therefore, client applications had to do the
      locking themselves. That locking is right now only achievable by
      using Avkon Api. The template code of the Qt Quick App wizard did
      exactly that.
      Now, Qt 4.7.2 has the screen orientation lock built in. That
      implementation was done for QTBUG-11785. No need to do that in the
      application code, anymore.
      
      This patch removes Avkon usage from the templates, using new enum keys
      and setting QWidget flags, just like Maemo5 does.
      
      Two Qt version checks/fixes:
      1) If the application tries to lock the orientation on Qt < 4.7.2,
         a warning is given that this won't work
      2) If Qt < 4.7.2 is used to build the application, the enum keys are
         not used directly but casted from constants
      
      Task-Number: QTCREATORBUG-3598
      Reviewed-by: ck
      d4e58902