1. 25 Jan, 2019 3 commits
  2. 24 Jan, 2019 9 commits
    • Nate Graham's avatar
      [Desktop theme KCM] Use new icon · cbe86e62
      Nate Graham authored
      Summary: Icon was just introduced with D18433. The new icon's name is such that the fallback icon will be `preferences-desktop-plasma`, which is already present in 3rd-party icon themes, so nothing will get broken.
      Test Plan: {F6561083}
      Reviewers: #vdg, #plasma, GB_2
      Reviewed By: #vdg, GB_2
      Subscribers: plasma-devel
      Tags: #plasma
      Differential Revision: https://phabricator.kde.org/D18441
    • Kai Uwe Broulik's avatar
      [Desktop Theme KCM] Support installing from remote locations · 12f4d353
      Kai Uwe Broulik authored
      Uses KIO to copy the file into temp folder for installation.
      The same as the other KCMs do.
      Differential Revision: https://phabricator.kde.org/D18498
    • 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
    • Kai Uwe Broulik's avatar
      Merge branch 'Plasma/5.15' · fdeb8bb3
      Kai Uwe Broulik authored
    • Kai Uwe Broulik's avatar
    • Kai Uwe Broulik's avatar
      [KRDB] Also try wildcard tooltip · c6bab929
      Kai Uwe Broulik authored
      It seems as though only tooltip background color was honored whereas text stayed at whatever default window text there was,
      leading to potentially unreadable text.
      BUG: 355540
      FIXED-IN: 5.12.8
      CHANGELOG: Fixed incorrect tooltip colors applied to GTK2 applications leading to unreadable text
      Differential Revision: https://phabricator.kde.org/D18482
    • Script Kiddy's avatar
      SVN_SILENT made messages (.desktop file) - always resolve ours · f8347abe
      Script Kiddy authored
      In case of conflict in i18n, keep the version of the branch "ours"
      To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
    • Kai Uwe Broulik's avatar
      [KRDB] Write correct tooltip colors into gtkrc in kcminit · c394dc46
      Kai Uwe Broulik authored
      kcminit for performance reasons is not desktop settings aware which means it won't load the plasma integration plugin and as such
      not apply the color scheme to Qt's widgets.
      When writing the GTK config, it would read them from kdeglobals directly. However, for tooltips it would use QToolTip::palette()
      which would then use Qt's default palette in kcminit. Use the QPalette we created from kdeglobals to get the tooltip colors instead.
      CCBUG: 355540
      Differential Revision: https://phabricator.kde.org/D18482
    • Script Kiddy's avatar
      SVN_SILENT made messages (.desktop file) - always resolve ours · 110e10e4
      Script Kiddy authored
      In case of conflict in i18n, keep the version of the branch "ours"
      To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
  3. 23 Jan, 2019 6 commits
  4. 22 Jan, 2019 4 commits
  5. 20 Jan, 2019 7 commits
  6. 19 Jan, 2019 4 commits
  7. 18 Jan, 2019 3 commits
  8. 17 Jan, 2019 4 commits