1. 03 Feb, 2020 2 commits
  2. 16 Jan, 2020 2 commits
  3. 15 Jan, 2020 1 commit
    • Dan Leinir Turthra Jensen's avatar
      Switch the Plasma Desktop KCMs to using KNewStuffQuick · 442c43b3
      Dan Leinir Turthra Jensen authored
      Summary:
      This switches the KCMs which previously used a bit of a hack to show the old Widgets based Get Hot New Stuff dialog from a button in the Qt Quick based KCMs so that they instead use the new KNewStuff Qt Quick submodule. The modules affected by this are:
      
      * Colors
      * Cursor Theme
      * Desktop Theme
      * Icons
      * KSplash
      
      Reviewers: mart, ngraham
      
      Reviewed By: mart, ngraham
      
      Subscribers: bcooksley, davidedmundson, ngraham, plasma-devel
      
      Tags: #plasma
      
      Differential Revision: https://phabricator.kde.org/D26544
      442c43b3
  4. 10 Jan, 2020 1 commit
    • David Redondo's avatar
      [Colors KCM] Correctly report whether saving is needed · 2cac0513
      David Redondo authored
      Summary:
      Previously the kcm always reported that a save is needed once a scheme had been
      marked for deletion. The correct way is to check if there are schemes that are
      currently marked for deletion. Also we don't need the firstTime workaround.
      
      Test Plan: Mark a scheme for deletion and undo that action
      
      Reviewers: #plasma, mart
      
      Reviewed By: #plasma, mart
      
      Subscribers: plasma-devel
      
      Tags: #plasma
      
      Differential Revision: https://phabricator.kde.org/D26526
      2cac0513
  5. 29 Nov, 2019 1 commit
  6. 13 Nov, 2019 1 commit
  7. 29 Aug, 2019 1 commit
  8. 06 Aug, 2019 1 commit
    • Jan Blackquill's avatar
      [kcm-colors] Export colorscheme to GTK color definitions · 2de7c944
      Jan Blackquill authored
      Summary:
      This exports the active colorscheme to ~/.config/gtk-3.0/colors.css and sets up ~/.config/gtk-3.0/gtk.css to read from it.
      This will do nothing visibly without changes to Breeze GTK made in D22877
      
      FEATURE: 356006
      FIXED-IN: 5.17.0
      
      Test Plan: See that ~/.config/gtk-3.0/colors.css is created, colorscheme is dumped correctly, and that gtk.css links to it.
      
      Reviewers: #plasma, ngraham, broulik
      
      Reviewed By: #plasma, ngraham, broulik
      
      Subscribers: ahiemstra, ngraham, davidre, broulik, plasma-devel
      
      Tags: #plasma
      
      Differential Revision: https://phabricator.kde.org/D22844
      2de7c944
  9. 04 Aug, 2019 1 commit
  10. 08 Mar, 2019 1 commit
  11. 13 Feb, 2019 1 commit
    • Filip Fila's avatar
      Make Appearance KCMs' labels consistent · 089612d2
      Filip Fila authored
      Summary:
      With the purpose of making KCMs more consistent and following the HIG, this patch does the following:
      
      - Converts all .desktop file "Comment" values into action(verb)-style labels
      - Drops the use of articles in "Comment" values
      - Changes the KAboutData i18n strings so that they match the respective KCM's name
      
      Reviewers: GB_2, #vdg, ngraham, #plasma
      
      Reviewed By: GB_2, #vdg, ngraham
      
      Subscribers: davidedmundson, broulik, plasma-devel
      
      Tags: #plasma
      
      Maniphest Tasks: T10273
      
      Differential Revision: https://phabricator.kde.org/D18903
      089612d2
  12. 25 Jan, 2019 1 commit
  13. 24 Jan, 2019 1 commit
    • Kai Uwe Broulik's avatar
      [Colors KCM] Port to new design · b52c0ceb
      Kai Uwe Broulik authored
      Overall the user experience has been streamlined and simplified a lot:
      
      * The "Default" theme option has been dropped in favor of having the "Defaults" button revert the selected theme to Breeze.
        While technically the old code made it read the hardcoded default colors in KColorScheme (which cause the window decoration
        to turn blue as it cannot write into KWin config like the theme files can), this change makes most sense from a UX POV.
      * The "Current" theme option has also been removed. Technically, when applying a theme the colors are copied into kdeglobals,
        so you could have a custom theme that is not an actual .colors file on disk. However, this is imho quite a niche usecase.
        Ideally, we showed a "Custom" theme as soon as the actual theme diverges from any theme file installed but that would require
        tediously comparing dozens of settings values which I don't think is feasible. At least when the color scheme name set in
        kdeglobals does not exist, a warning is now displayed.
      * The "Apply to non-Qt applications checkbox" which isn't something one would want to uncheck has been removed.
        It is still read from kcmdisplayrc for those who really want to disable it but there is no user-visible checkbox anymore.
      
      KColorSchemeEditor is now completely disentangled from the KCM and is merely launched as separate process:
      
      * When editing a system scheme, upon clicking "Save" the user is prompted to type a new scheme name. This ensures that any custom
        scheme is always present on disk reducing the need for a "Current" entry. When the dialog is then closed, the newly saved theme
        is selected.
      * When editing a user scheme, the "Save" button turns into "Apply", which when clicked updates the scheme with any changes made in
        the dialog (different behavior from when kcolorschemeeditor is launched standalone, where "Save" is always essentially "Save As")
      
      The rewrite also comes with all the goodies we got in the other new KCMs, such as the ability to drop a .colors file into the view
      to install it (even from remote locations), undo deletion until you apply your changes, double click for quick apply, and so on.
      
      BUG: 307216
      FIXED-IN: 5.16.0
      
      Differential Revision: https://phabricator.kde.org/D12278
      b52c0ceb