1. 22 Feb, 2017 1 commit
  2. 13 Dec, 2016 1 commit
  3. 08 Nov, 2016 1 commit
    • Ulf Hermann's avatar
      Theme: Use QVariantMap for theme properties · 08b78020
      Ulf Hermann authored
      QML can directly mirror this into a JavaScript object, so there is no
      need to manually copy the values into a different container. Also,
      QQmlPropertyMap is very expensive as it will listen to changes to any
      value in the map. We never use this. It would be entirely enough to
      update the whole map at once if we ever want to update the theme at
      Change-Id: Ie2b549e9af51d620801808c87d6f659cc7a06c04
      Reviewed-by: default avatarThomas Hartmann <Thomas.Hartmann@theqtcompany.com>
  4. 02 Nov, 2016 1 commit
    • Eike Ziller's avatar
      Core: Refactor argument handling · 05bf915c
      Eike Ziller authored
      Split up getting the data from the arguments list and actually applying
      the values, and move the details of theme creation and application to
      better places.
      This gets rid of ugly control flow details like that
      CorePlugin::initialize created the action manager before calling
      parseArguments, because that is needed to apply the presentation mode
      argument setting, and parseArguments created the main window because
      that needs to be created _after_ setting the theme (which can be
      overridden by command line argument), but _before_ applying the override
      color argument setting.
      Change-Id: I9c99305b6efbfcc4b37cea9e5c70d816a621963b
      Reviewed-by: David Schulz's avatarDavid Schulz <david.schulz@qt.io>
  5. 22 Jul, 2016 1 commit
  6. 05 Jul, 2016 1 commit
  7. 21 Jun, 2016 1 commit
  8. 29 Jan, 2016 1 commit
  9. 19 Jan, 2016 1 commit
  10. 14 Jan, 2016 1 commit
  11. 06 Nov, 2015 1 commit
    • Eike Ziller's avatar
      Themes: Fix issues with restoring themes. · 11f61627
      Eike Ziller authored
      Themes from the user config where not restored correctly.
      Improve error handling when no themes are found
      in case of broken installations.
      Cleanly differentiate between theme "id" (currently complete basename of
      theme file) and theme "displayName" (as specified as a property in the
      theme file).
      Remove convoluted broken code that tried to allow using an absolute file
      path for a theme on the command line and require themes to be installed
      either in Qt Creator globally or in the user settings path.
      In general stream line the code.
      Task-number: QTCREATORBUG-15113
      Task-number: QTCREATORBUG-15233
      Change-Id: I014a4314e8bea27422ed4c42462cf16f4220698b
      Reviewed-by: default avatarAlessandro Portale <alessandro.portale@theqtcompany.com>
  12. 08 Sep, 2015 1 commit
  13. 08 Jul, 2015 1 commit
  14. 30 Mar, 2015 2 commits
  15. 26 Mar, 2015 1 commit
  16. 27 Feb, 2015 1 commit
  17. 10 Feb, 2015 1 commit
  18. 16 Jan, 2015 1 commit
  19. 10 Dec, 2014 1 commit
  20. 21 Nov, 2014 1 commit
  21. 20 Nov, 2014 2 commits
  22. 06 Nov, 2014 1 commit
  23. 22 Oct, 2014 1 commit
  24. 17 Oct, 2014 3 commits
  25. 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>
  26. 15 Oct, 2014 2 commits
    • Alessandro Portale's avatar
      Fix build · fa19530c
      Alessandro Portale authored
      Change-Id: I7d0b2a827b76a0715c8e257dd6b45e7e8b11e064
      Reviewed-by: default avatarAlessandro Portale <alessandro.portale@digia.com>
    • 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
      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
      - Introduce class Theme, defining the interface how to access theme
        specific settings. The class reads a .creatortheme file (INI file, via
        - Define named colors in the [Palette] section
          (see dark.creatortheme for example usage)
        - Use either named colors of AARRGGBB (hex) in the [Colors]
        - 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
      - 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
      - Themes can be modified via the 'Themes' tab in the environment
      * 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>