1. 28 Oct, 2016 1 commit
  2. 21 Oct, 2016 1 commit
  3. 09 Jun, 2016 1 commit
  4. 26 Apr, 2016 1 commit
  5. 29 Jan, 2016 1 commit
  6. 22 Jan, 2016 1 commit
  7. 21 Jan, 2016 2 commits
  8. 20 Jan, 2016 1 commit
  9. 14 Jan, 2016 2 commits
  10. 25 Nov, 2015 1 commit
    • Alessandro Portale's avatar
      Themed Icons: Introduce Utils::Icon · 033862f3
      Alessandro Portale authored
      Instead of describing icons via file name or in the themed icons case
      a string that is a list of mask/color pairs, we have now a class for it.
      Icons are now listed in per-plugin *icons.h headers.
      RunControl::m_icon was The only place left where an icon property was in
      fact a string. This patch changes that member to be a Utils::Icon.
      Change-Id: Ibcfa8bb25e6d2e330c567ee7ccc0b97ead603177
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
  11. 04 Nov, 2015 1 commit
    • hjk's avatar
      Core: Replace ICoreListener by std::functions · e6a98f36
      hjk authored
      ICoreListener::coreAboutToClose() remains in the core,
      ICoreListener::editorAboutToClose() is handled by a new
      EditorManager::addCloseEditorListener() function.
      This removes the need for some boiler plate code resulting
      from the need to implement the interface in custom classes
      (DesignModeCoreListener, EditorClosingCoreListener,
      PojectEplorer::CoreListener and VcsBase::CoreListener).
      Change-Id: Ie554c987b5455b555be6d77b77e4013639201d22
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
  12. 01 Sep, 2015 1 commit
  13. 28 Aug, 2015 1 commit
  14. 04 May, 2015 1 commit
    • Tobias Hunger's avatar
      Vcs: Split up VcsCommand · eec0a032
      Tobias Hunger authored
      Move the biggest chunk into Utils::ShellCommand, add some Qt Creator
      specific magic in Core::ShellCommand and leave the rest in
      Change-Id: I5fe6f7076e96023ad2164bcfaacfb3b65a7ff8a8
      Reviewed-by: Orgad Shaneh's avatarOrgad Shaneh <orgads@gmail.com>
  15. 01 Apr, 2015 1 commit
  16. 17 Feb, 2015 1 commit
  17. 13 Feb, 2015 1 commit
  18. 14 Jan, 2015 1 commit
  19. 19 Dec, 2014 1 commit
  20. 25 Nov, 2014 1 commit
  21. 24 Nov, 2014 1 commit
  22. 07 Nov, 2014 1 commit
  23. 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
      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>
  24. 14 Oct, 2014 1 commit
    • hjk's avatar
      VariableChooser: Rework · 3119d93b
      hjk authored
      Allow multiple expanders to be registered for lineedits, e.g. a
      local and the global ones, and actually show them.
      Use a tree view in the chooser for somewhat more structured display.
      Change-Id: I769f92144e5249f45e54381de52aa6973eb20118
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@theqtcompany.com>
  25. 26 Sep, 2014 1 commit
  26. 18 Sep, 2014 1 commit
  27. 16 Sep, 2014 1 commit
  28. 15 Sep, 2014 1 commit
  29. 08 Sep, 2014 1 commit
  30. 13 Aug, 2014 1 commit
  31. 24 Jul, 2014 1 commit
  32. 22 Jul, 2014 1 commit
  33. 18 Jul, 2014 1 commit
    • Eike Ziller's avatar
      Core: Refactor handling of "window state" actions out of MainWindow · fe5b3a39
      Eike Ziller authored
      Currently the actions for fullscreen, minimize and zoom only apply to
      the main window, even if a different window is active.
      Refactor the handling of these actions into a WindowSupport class, and
      use that instead for the main window. In a second step, this will be
      used to add the functionality to the corresponding external windows
      (e.g. help and editor windows)
      Change-Id: Ief2c880f40948c3bb724196d6e0cfe888b8ece89
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
  34. 11 Jul, 2014 1 commit
  35. 01 Jul, 2014 1 commit
  36. 27 Jun, 2014 1 commit
  37. 06 Jun, 2014 1 commit
  38. 05 Jun, 2014 1 commit