1. 29 Oct, 2015 1 commit
  2. 16 Sep, 2015 1 commit
  3. 02 Sep, 2015 2 commits
  4. 21 Aug, 2015 1 commit
  5. 18 Aug, 2015 1 commit
  6. 22 Jul, 2015 1 commit
  7. 23 Jun, 2015 1 commit
  8. 23 Apr, 2015 1 commit
  9. 23 Mar, 2015 1 commit
  10. 17 Mar, 2015 1 commit
  11. 16 Mar, 2015 2 commits
  12. 02 Mar, 2015 1 commit
  13. 25 Feb, 2015 1 commit
  14. 18 Feb, 2015 1 commit
  15. 17 Feb, 2015 1 commit
  16. 13 Feb, 2015 1 commit
  17. 12 Feb, 2015 1 commit
  18. 02 Feb, 2015 1 commit
  19. 29 Jan, 2015 1 commit
  20. 23 Jan, 2015 2 commits
  21. 16 Jan, 2015 1 commit
  22. 14 Jan, 2015 1 commit
    • Daniel Teske's avatar
      Refactor ProjectExplorer::Node and remove NodesWatcher · 70c9c51e
      Daniel Teske authored
      
      
      The idea behind NodesWatcher was that it was the central place
      to catch node related signals, so that users didn't need to
      connect to each individual node and the nodes didn't need to
      be QObjects. Somehow Nodes ended up being QObjects anyway.
      
      Both the recently added ProjectTree and the FlatModels consume
      the signals the NodesWatcher sends. Unfortunately there's a
      ordering dependency between the ProjectTree and the FlatModels.
      
      This patch removes all NodesWatcher and instead makes the
      ProjectTree singleton the emitter of various project tree
      related signals. The ProjectTree also ensures that the ordering
      between the FlatModel and itself is taken into account.
      
      And it makes Node not derive from QObject, saving some memory
      in that process.
      
      Task-number: QTCREATORBUG-13756
      Change-Id: I8b0d357863f1dc1d2d440ce8172502594138b9fb
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@theqtcompany.com>
      70c9c51e
  23. 12 Jan, 2015 1 commit
  24. 08 Jan, 2015 1 commit
  25. 16 Dec, 2014 2 commits
  26. 03 Dec, 2014 1 commit
  27. 20 Nov, 2014 1 commit
  28. 11 Nov, 2014 1 commit
  29. 06 Nov, 2014 1 commit
  30. 27 Oct, 2014 2 commits
  31. 20 Oct, 2014 1 commit
  32. 16 Oct, 2014 1 commit
    • Alessandro Portale's avatar
      Cleanup of Theming · a18b0673
      Alessandro Portale authored
      
      
      A theme is supposed to provide colors, flags and images. This change
      removes functions from Theme which do not just return simple data.
      Also ManhattanStyle and Theme get separated a bit.
      
      Change-Id: I2fab26ee38b858fefb55920eb219f84abcfaac18
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
      a18b0673
  33. 15 Oct, 2014 1 commit
    • Thorben Kroeger's avatar
      Implement theming for QtCreator · 84f5585b
      Thorben Kroeger authored
      Adds a 'Theme' tab to the environment settings and a '-theme' command
      line option.
      A theme is a combination of colors, gradients, flags and style
      information.
      
      There are two themes:
      - 'default': preserves the current default look
      - 'dark': uses a more flat for many widgets, dark color theme
        for everything
      
      This does not use a stylesheet (too limited), but rather sets
      the palette via C++ and modifies drawing behavior.
      Overall, the look is more flat (removed some gradients and bevels).
      
      Tested on Ubuntu 14.04 using Qt 5.4 and running on a KDE
      Desktop (Oxygen base style).
      
      For a screenshot, see
      https://gist.github.com/thorbenk/5ab06bea726de0aa7473
      
      
      
      Changes:
      - Introduce class Theme, defining the interface how to access theme
        specific settings. The class reads a .creatortheme file (INI file, via
        QSettings)
      
        - Define named colors in the [Palette] section
          (see dark.creatortheme for example usage)
      
        - Use either named colors of AARRGGBB (hex) in the [Colors]
          section
      
        - A file ending with .creatortheme may be supplied
          to the '-theme' command line option
      
      - A global Theme instance can be accessed via creatorTheme()
      
      - Query colors, gradients, icons and flags from the theme
        were possible (TODO: use this in more places...)
      
      - There are very many color roles. It seems better to me
        to describe the role clearly, and then to consolidate later
        in the actual theme by assigning the same color.
        For example, one can set the text color of the output pane button
        individualy.
      
      - Many elements are also drawn differently.
        For the dark theme, I wanted to have a flatter look.
        - Introduce Theme::WidgetStyle enum, for now {Original, Flat}.
        - The theme specifies which kind of widget style it wants.
        - The drawing code queries the theme's style flag and
          switches between the original, gradient based look and
          the new, flat look.
      
      - Create some custom icons which look better on dark background
        (wip, currently folder/file icons)
      
      - Let ManhattanStyle draw some elements for non-panelwidgets, too
        (open/close arrows in QTreeView, custom folder/file icons)
      
      - For the welcomescreen, pass the WelcomeTheme class.
        WelcomeTheme exposes theme colors as Q_PROPERTY accessible from
        .qml
      
      - Themes can be modified via the 'Themes' tab in the environment
        settings.
      
      TODO:
      * Unify image handling
      * Avoid style name references
      * Fix gradients
      
      Change-Id: I92c2050ab0fb327649ea1eff4adec973d2073944
      Reviewed-by: default avatarThomas Hartmann <Thomas.Hartmann@digia.com>
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
      84f5585b
  34. 10 Oct, 2014 2 commits