1. 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>
  2. 09 Oct, 2015 1 commit
  3. 30 Sep, 2015 1 commit
  4. 01 Sep, 2015 1 commit
  5. 15 Jun, 2015 1 commit
    • Jochen Becher's avatar
      Introduce dragging for all explorer nodes. · 431b25ad
      Jochen Becher authored
      Extend drop support with variant values. A drop may be a file drop or a
      value drop or both.
      Rename Utils::FileDropSupport to Utils::DropSupport and add methods to
      add not only files but any QVariant value to the mime data. Project
      explorer adds dragged nodes (which will be needed for future ModelEditor
      Change-Id: I799542c60fdecb3e64af0d3ba47b6caa9adbcfd7
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
  6. 01 Jun, 2015 1 commit
  7. 09 Mar, 2015 1 commit
  8. 24 Feb, 2015 1 commit
  9. 19 Feb, 2015 1 commit
  10. 17 Feb, 2015 1 commit
  11. 16 Feb, 2015 1 commit
  12. 16 Jan, 2015 1 commit
  13. 12 Jan, 2015 1 commit
    • Eike Ziller's avatar
      ActionManager: transfer ownership from main window to core plugin · e40477cc
      Eike Ziller authored
      Also make a bit less dependent on main window:
      - Menus do not need to start with main window as parent.
      - Centering the presentation label on the main window is wrong in the
      presence of extra windows anyhow. It should be centered on the active
      Unfortunately, actions still must be added to the main window, because
      actions that are not children of visible widgets do not trigger.
      Change-Id: Ibb99644a3723de476db465ebe6a9cdc0820ea692
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@theqtcompany.com>
  14. 26 Nov, 2014 1 commit
    • Orgad Shaneh's avatar
      Core: Cosmetics · 7f341580
      Orgad Shaneh authored
      * Remove redundant namespace qualifiers
      * Qt5-ify some signal/slot connections
      * Replace some using Core::Internal with explicit namespace scopes
      Change-Id: Id1aae05e2c6fc2992c2716e1f8f9e985c6e56122
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
  15. 07 Nov, 2014 1 commit
  16. 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>
  17. 14 Oct, 2014 1 commit
  18. 09 Oct, 2014 1 commit
  19. 23 Sep, 2014 1 commit
  20. 16 Sep, 2014 1 commit
  21. 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>
  22. 11 Jul, 2014 1 commit
  23. 09 Jul, 2014 1 commit
  24. 02 Jul, 2014 1 commit
  25. 26 May, 2014 1 commit
    • Tobias Hunger's avatar
      IWizard->IWizardFactory · a8e89101
      Tobias Hunger authored
      Start at splitting up the wizard functionality a bit. Currently
      it is a factory but also contains a lot of logic that is invoked by
      the real wizard dialogs.
      This change renames/moves a couple of things only.
      Change-Id: I1fa114ee3ee262f7c0690841f361bbf09e674725
      Reviewed-by: Orgad Shaneh's avatarOrgad Shaneh <orgads@gmail.com>
  26. 05 Mar, 2014 1 commit
  27. 03 Mar, 2014 1 commit
  28. 13 Jan, 2014 1 commit
  29. 08 Jan, 2014 1 commit
  30. 03 Sep, 2013 1 commit
  31. 02 Sep, 2013 2 commits
  32. 01 Jul, 2013 2 commits
  33. 21 May, 2013 4 commits
  34. 15 Mar, 2013 2 commits