1. 15 Dec, 2017 1 commit
    • hjk's avatar
      De-emphasize PluginManager::getObjects<Type>() · cc883023
      hjk authored
      ... by additionally keeping local (currently non-owning) pools per
      "interesting" type.
      
      Current situation:
        - The global object pool does not scale well for looking up
          objects, as iteration plus qobject_cast typically iterates
          over all pooled objects.
        - User code that can use typed results from the object
          pool need to have access to the full type definition anyway,
          i.e.  depend on the plugin of the target class anyway.
      
      The patch here solves the scaling problem is to have local
      type-specific pools to which objects register in their
      constructors and deregister in their destructors.
      
      This patch here does *not* change the ownership model of the
      pooled objects, however, it opens the possibility to change
      the ownership model per type (e.g. by not putting things into
      the global pool at all anymore and make the local pool 'owning')
      and the intent is to handle that in later patchs.
      
      Even without the follow-up patches this here is a performance
      improvement for the cases that access the local pools instead
      the global one, i.e. "practically all".
      
      Change-Id: Ib11a42df2c4ecf5e1155534730083a520dd1995b
      Reviewed-by: Eike Ziller's avatarEike Ziller <eike.ziller@qt.io>
      Reviewed-by: Christian Kandeler's avatarChristian Kandeler <christian.kandeler@qt.io>
      cc883023
  2. 30 Mar, 2016 1 commit
  3. 20 Jan, 2016 1 commit
  4. 19 Jan, 2016 1 commit
  5. 05 Mar, 2015 1 commit
  6. 13 Feb, 2015 1 commit
    • Daniel Teske's avatar
      Android: Set correct ANDROID_NDK_PLATFORM · e7b90b86
      Daniel Teske authored
      Introduce the class AndroidQmakeBuildConfiguration whose purpose is
      to set the environment variable. Modify the Factory to create
      buildconfigurations of that type and fix restore/clone to also
      take the factories' priorities into account.
      
      Change-Id: Icb377fa9211cd3564c36b60cf7c5f7dd84fcab50
      Reviewed-by: default avatarBogDan Vatra <bogdan@kde.org>
      e7b90b86
  7. 06 Feb, 2015 1 commit
  8. 16 Jan, 2015 1 commit
  9. 15 Oct, 2014 1 commit
  10. 25 Sep, 2014 1 commit
    • BogDan Vatra's avatar
      Android: Say hello to gradle! · 3bcae525
      BogDan Vatra authored
      Switching from Ant to Gradle brings lots of advantages:
       - it is way faster when rebuilding (25-50% faster than ant).
       - it enables first class Android Studio integration.
       - adding Android Extras libs (e.g. Google Play services, OBB, etc.) to
         your project is now painless.
      
      [ChangeLog][Android] Added Gradle support to build the APK.
      
      Change-Id: Iee492954f8ffb2c22e6ab14a8a25faf644de9a51
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
      3bcae525
  11. 08 Aug, 2014 1 commit
  12. 21 Jul, 2014 2 commits
    • BogDan Vatra's avatar
      Move qmake specific part to qmake plugin, generalize android support · 64e5a543
      BogDan Vatra authored
      - Split up androiddeployqt into two steps: One building the apk,
        and one deploying it to the device.
      - The build apk step base class AndroidBuildApkStep is ihneritaged by
        the qmake specific class QmakeAndroidBuildApkStep.
      - The deployment step is still called androiddeployqt
      - Move all qmake specific code to the qmakeprojectmanager plguin
      - Flip the depencency between the android and qmake plugin, now
        the qmake plugin depends on the android plugin, implementing
        a interface the android plugin provides.
      
      - Note: This removes the debug deployment for now.
      
      Change-Id: I1c386640159ed14b637668abde8eb3b9009ab803
      Reviewed-by: default avatarBogDan Vatra <bogdan@kde.org>
      64e5a543
    • BogDan Vatra's avatar
      AndroidDebugSupport: Split up into general and qmake specific part · 6a4c47b1
      BogDan Vatra authored
      Introudce AndroidQtSupport. The derived class will eventually move to
      the qmakeprojectmanager plugin.
      
      Change-Id: I3fdc98259644fe718eb15aa9bd11d92dc0cdb1af
      Reviewed-by: default avatarBogDan Vatra <bogdan@kde.org>
      6a4c47b1
  13. 08 Jan, 2014 1 commit
  14. 10 Dec, 2013 1 commit
    • Eike Ziller's avatar
      Preferences: Add default implementation for filtering · deb43b4c
      Eike Ziller authored
      The default "matches" method now takes the widget and looks for all
      child labels, checkboxes, push buttons and group boxes.
      Because of that, the former "createWidget" method
      can be called multiple times without creating a new widget
      (-->widget()), and the "finished" method must ensure that the created
      widget gets deleted, since not all widgets that were created are added
      to the UI anymore.
      
      Change-Id: Ia231c7c78dd8819146668e6447d36d22e7836904
      Reviewed-by: default avatarEike Ziller <eike.ziller@digia.com>
      deb43b4c
  15. 29 Jan, 2013 1 commit
  16. 05 Oct, 2012 1 commit
  17. 19 Jul, 2012 1 commit
  18. 23 May, 2012 1 commit
  19. 24 Apr, 2012 1 commit
  20. 08 Mar, 2012 1 commit
  21. 26 Jan, 2012 1 commit
  22. 03 Nov, 2011 1 commit
  23. 22 Jul, 2011 1 commit
  24. 06 May, 2011 1 commit
  25. 13 Apr, 2011 1 commit
  26. 22 Feb, 2011 1 commit
  27. 21 Feb, 2011 1 commit
    • Tobias Hunger's avatar
      ToolChain: Refactor toolchain support · 8d0c4772
      Tobias Hunger authored
      Refactor ToolChains in Qt Creator:
      
       * Allow for several toolchains of the same type
       * Be smarter wrt. guessing what kind of output a toolchain
         produces. This allows us to eventually handle e.g. embedded
         linux setups way better than before.
       * Be smarter wrt. guessing what kind of environment a Qt version
         needs.
       * Improve auto-detection of toolchains a bit
       * Decide on which debugger to use based on the kind of output
         produced by the compiler.
       * Add options page to configure toolchains
       * Remove toolchain related options from the Qt version dialog
      
      Reviewed-by: dt
      8d0c4772
  28. 12 Jan, 2011 2 commits
  29. 17 Dec, 2010 1 commit
  30. 06 Dec, 2010 1 commit
  31. 15 Nov, 2010 1 commit
    • hjk's avatar
      debugger: Refactor breakpoint handling. · 8ae541b3
      hjk authored
      The breakpoints are now (fairly) tightly guarded by the BreakpointHandler.
      Engines and Views are only supposed to refer to them by id. They also have
      individual states now. The breakpoint data is split into a "user requested"
      "fixed" part in BreakpointData and the engines' acknowledged data in a new
      struct BreakpointResponse.
      
      TODO: Move m_state and m_engine members to BreakpointResponse. Fix regressions
      in the marker handling.
      8ae541b3
  32. 02 Nov, 2010 1 commit
  33. 22 Jun, 2010 1 commit
    • hjk's avatar
      debugger: The DebuggerEngine refactoring. · 6a6cba55
      hjk authored
      This replaces the (de facto) singleton engines and data handlers by classes
      that are instantiated per run. The DebuggerRunControl will now create an
      object of (a class derived from) DebuggerEngine that contains all the relevant
      "dynamic" data.
      
      DebuggerManager is no more. The "singleton" bits are merged into DebuggerPlugin,
      whereas the data bits went to DebuggerEngine.
      
      There is no formal notion of a "current" DebuggerEngine. However, as there's
      only one DebuggerEngine at a time that has its data models connected to the
      view, there's still some "de facto" notion of a "current" engine. Calling
      SomeModel::setData(int role, QVariant data) with custom role is used as the
      primary dispatch mechanism from the views to the "current" data models
      (and the engine, as all data models know their engine).
      6a6cba55
  34. 08 Apr, 2010 1 commit
  35. 26 Mar, 2010 1 commit
  36. 05 Mar, 2010 1 commit
  37. 07 Jan, 2010 2 commits
    • Tobias Hunger's avatar
      Make method naming more consistent. · a6ad7737
      Tobias Hunger authored
        * Use id() for methods returning a string used to represent
          some type of object.
        * Use displayName() for strings that are meant to be user
          visible.
        * Quieten some warnings while touching the files anyway.
        * Move Factories to their products in the plugins where that
          was not done before.
      
      Reviewed-by: dt
      a6ad7737
    • Tobias Hunger's avatar
      Add copyright headers. · f5a893bc
      Tobias Hunger authored
       * Make sure all non-empty source files found below ./src have
         a copyright header.
      
      Reviewed-by: con
      f5a893bc