[Breeze] [Bug 355906] Please consider unification for themes' data paths.
Sebastian Kügler via KDE Bugzilla
bugzilla_noreply at kde.org
Thu Nov 26 13:40:03 UTC 2015
https://bugs.kde.org/show_bug.cgi?id=355906
--- Comment #3 from Sebastian Kügler <sebas at kde.org> ---
It's going to vastly increase lookup time in many cases, namely any time you
look up a specific theme or a list of themes. (You now have to dive into
subdirectories.) Currently, we can (more or less) just list a subdirectory with
e.g. all plasma themes, and then we have our list of themes. Some bits need
metadata files installed so the "theme" (in the widest sense of the word)
simply cannot be contained to some directory under /usr/share/themes.
The logic you're missing between QtCurve (obviously you're looking for the KDE4
version) and Breeze (apparently Frameworks 5 based version) is that they're
simply doing entirely different things.
What you're missing is that "themes" is a concept that makes sense to the user,
for developers and system integrators, you need the type of theme, they can be
collections of images (icons), SVGs (icons, Plasma themes), stylesheets
(QtCurve, new-style GNOME), or C++ code (Qt styles), QML (Plasma look and feel
packages), binary plugins (window decorations) which means they need different
treatment.
Now ask around distros how happily they put compiled binaries into /usr/share
(they belong under /lib or /usr/lib, depending).
"Please put all themes under /usr/share/themes" is ignoring that complexity,
therefore it's not feasible to do so as the bug potential, performance penalty
and work involved does IMO not justify the benefit you lined out.
Note that if you include subdirectories in your zip of themes, anyway, you're
not bound to one directory under /usr/share/themes, you can do the exact same
thing and put it into different directories (that's what package managers such
as RPM actually do, they unzip a directory structure to system directories).
That said, it sounds like a recipe for disaster to encourage theme editors to
do this. Let distros handle it, or tools like plasmapkg (which has all the
logic to figure what to install where, and it's not simple logic that can
easily be replaced with "well, put everything there, in subdirectories").
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Plasma-devel
mailing list