1. 26 Jan, 2015 2 commits
  2. 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
  3. 15 Oct, 2014 3 commits
    • Tobias Hunger's avatar
      JsonWizard: Replace CppClassWizard with a JsonWizard · 50df8aa9
      Tobias Hunger authored
      Change-Id: I4e1aeea4ccd1087b5e804e9ba4c2aa8fde4f4fcb
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
      50df8aa9
    • 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
    • hjk's avatar
      TextEditor: Factory cosmetics · eacaf93a
      hjk authored
      Pimpl, add some convenience setters.
      
      Change-Id: I525c080179fddab6fe2bd2270505fdbf33e56be2
      Reviewed-by: default avatarDavid Schulz <david.schulz@digia.com>
      eacaf93a
  4. 09 Oct, 2014 1 commit
  5. 02 Oct, 2014 1 commit
  6. 30 Sep, 2014 2 commits
  7. 29 Sep, 2014 1 commit
  8. 19 Sep, 2014 1 commit
  9. 02 Sep, 2014 2 commits
  10. 27 Aug, 2014 3 commits
  11. 25 Aug, 2014 1 commit
    • Nikolai Kosjar's avatar
      C++: Base parsing on editor document instead of widget · 89bd4ee3
      Nikolai Kosjar authored
      This mainly takes CppEditorSupport apart.
      
      * Parsing is now invoked by CPPEditorDocument itself by listening to
        QTextDocument::contentsChanged().
      
      * Upon construction and destruction CPPEditorDocument creates and
        deletes an EditorDocumentHandle for (un)registration in the model
        manager. This handle provides everything to generate the working copy
        and to access the editor document processor.
      
      * A CPPEditorDocument owns a BaseEditorDocumentProcessor instance that
        controls parsing, semantic info recalculation and the semantic
        highlighting for the document. This is more or less what is left from
        CppEditorSupport and can be considered as the backend of a
        CPPEditorDocument. CPPEditorDocument itself is quite small.
      
          * BuiltinEditorDocumentProcessor and ClangEditorDocumentProcessor
            derive from BaseEditorDocumentProcessor and implement the gaps.
      
          * Since the semantic info calculation was bound to the widget, it
            also calculated the local uses, which depend on the cursor
            position. This calculation got moved into the extracted class
            UseSeletionsUpdater in the cppeditor plugin, which is run once the
            cursor position changes or the semantic info document is updated.
      
          * Some more logic got extracted:
      	- SemanticInfoUpdater (logic was in CppEditorSupport)
      	- SemanticHighlighter (logic was in CppEditorSupport)
      
          * The *Parser and *Processor classes can be easily accessed by the
            static function get().
      
      * CppHighlightingSupport is gone since it turned out to be useless.
      
      * The editor dependency in CompletionAssistProviders is gone since we
        actually only need the file path now.
      
      Change-Id: I49d3a7bd138c5ed9620123e34480772535156508
      Reviewed-by: Orgad Shaneh's avatarOrgad Shaneh <orgads@gmail.com>
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      89bd4ee3
  12. 22 Aug, 2014 1 commit
  13. 20 Aug, 2014 1 commit
  14. 19 Aug, 2014 1 commit
  15. 18 Aug, 2014 1 commit
  16. 31 Jul, 2014 1 commit
  17. 26 Jun, 2014 1 commit
  18. 13 Jun, 2014 1 commit
  19. 10 Jun, 2014 1 commit
  20. 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>
      a8e89101
  21. 05 Mar, 2014 1 commit
  22. 08 Jan, 2014 2 commits
  23. 07 Jan, 2014 1 commit
  24. 12 Dec, 2013 2 commits
  25. 11 Dec, 2013 1 commit
  26. 21 Nov, 2013 1 commit
  27. 24 Oct, 2013 1 commit
  28. 21 Oct, 2013 2 commits
  29. 10 Oct, 2013 1 commit
  30. 04 Oct, 2013 1 commit