1. 17 Oct, 2014 1 commit
  2. 16 Oct, 2014 4 commits
  3. 15 Oct, 2014 3 commits
    • Alessandro Portale's avatar
      Fix build · fa19530c
      Alessandro Portale authored
      Change-Id: I7d0b2a827b76a0715c8e257dd6b45e7e8b11e064
      Reviewed-by: default avatarAlessandro Portale <alessandro.portale@digia.com>
      fa19530c
    • 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
    • Eike Ziller's avatar
      License update. · 9c7019f0
      Eike Ziller authored
      Change-Id: I0acde2c3b995693de682679471f03af85bdd0a61
      Reviewed-by: default avatarAlessandro Portale <alessandro.portale@digia.com>
      9c7019f0
  4. 14 Oct, 2014 3 commits
  5. 13 Oct, 2014 1 commit
  6. 10 Oct, 2014 2 commits
  7. 09 Oct, 2014 2 commits
  8. 30 Sep, 2014 1 commit
  9. 25 Sep, 2014 2 commits
  10. 23 Sep, 2014 1 commit
  11. 18 Sep, 2014 2 commits
    • Tobias Hunger's avatar
      Core: Add a basic extension for the JsExpander · f5d48bf3
      Tobias Hunger authored
      This adds a "Utils" object to the Js runtime offered by the
      JsExpander that adds some useful functions.
      
      Mostly file name mangling and finding preferred extension
      from the MIME type database.
      
      Change-Id: I907dae7f295167667ac2ae81461bbff16dc98ef4
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
      f5d48bf3
    • Orgad Shaneh's avatar
      Debugger: Support setting substitute path by regexp · f0e2708d
      Orgad Shaneh authored
      This is useful when there are multiple build machines with different
      path, and the user would like to match anything up to some known
      directory to his local project (variable support will also be useful -
      will try to add that later).
      
      Syntax: (/home/.*)/KnownSubdir -> /home/my/project
      
      Capture group will be replaced by the value.
      
      In this example the substitute path will be (in case a source string
      found such as /home/SomeUser/SomeProject/KnownSubdir/foo.cpp):
      /home/SomeUser/SomeProject -> /home/my/project
      
      Change-Id: I19d03c9388161d8456a86676086dcb06dc3d7370
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
      f0e2708d
  12. 17 Sep, 2014 1 commit
  13. 16 Sep, 2014 3 commits
  14. 15 Sep, 2014 1 commit
  15. 12 Sep, 2014 3 commits
  16. 11 Sep, 2014 1 commit
  17. 10 Sep, 2014 1 commit
  18. 08 Sep, 2014 2 commits
    • Erik Verbruggen's avatar
      Utils: bring QtConcurrent::run into the current century. · 300c48e8
      Erik Verbruggen authored
      .. by adding support to pass in a std::function (which includes lambdas)
      as the function to run. The run function only takes functors that have
      a QFutureInterface& as parameter, because a lambda can already capture
      anything that would be passed in on invocation. Parameter-less
      std::function<>s are already handled by QtConcurrent (in Qt).
      
      To use it, you'll have to explicitly set the template parameter T on the
      call.
      
      Change-Id: Ie145fc3245d59fdea9d4703dab155ce9100eff89
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
      300c48e8
    • Christian Kandeler's avatar
      Remove Qt version checks. · 847f10e9
      Christian Kandeler authored
      Qt 5.3 is the minimum requirement these days. Remove all fallback code
      from sources and project files.
      
      Change-Id: If6188a471197acadda4d6baee71804ba1a8026c6
      Reviewed-by: default avatarEike Ziller <eike.ziller@digia.com>
      847f10e9
  19. 04 Sep, 2014 1 commit
  20. 03 Sep, 2014 1 commit
  21. 02 Sep, 2014 1 commit
  22. 29 Aug, 2014 1 commit
    • Christian Kandeler's avatar
      Do not use deprecated Qt functionality. · 1d5091e4
      Christian Kandeler authored
      Replace all* remaining deprecated Qt 4 functions with
      their Qt 5 counterparts. This means we no longer need to
      define the QT_DISABLE_DEPRECATED_BEFORE macro.
      This patch is relatively small because most source-compatible
      changes of this kind have been done before.
      
      * The one exception is the QmlDesigner, which uses QWeakPointer
      in a deprecated way all over the place.
      
      Change-Id: Id4b839c6685f3b5bdf2b89137f95231758ec53c7
      Reviewed-by: default avatarEike Ziller <eike.ziller@digia.com>
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
      1d5091e4
  23. 27 Aug, 2014 1 commit
  24. 26 Aug, 2014 1 commit