[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #1

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #2 from vladimir-...@yandex.ru --- > what exactly falls under themes? Icon themes? Qt styles? Plasma themes? GTK > themes? Firefox themes? (I could go on, this list is almost endless.) Well, everything you've listed, except icon themes,

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #3 from Sebastian Kügler --- 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

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com ---

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #5 from Martin Gräßlin --- Sorry, but I have to agree with sebas here. If I consider this for kwin, I must say it's horrible from the lookup perspective as we need to be fast at startup. With the proposal we cannot

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #6 from vladimir-...@yandex.ru --- > it sounds like a recipe for disaster to encourage theme editors to do this. No disaster has ever happened for software and themes that follow this convention. > What you're missing is that "themes" is

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #7 from Martin Gräßlin --- > I'm not missing this. Binary plugins are usually part of engines, and that > is completely different story. To clarify, Qt styles are analogous to GTK > engines and are NOT themes. Themes are

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #8 from vladimir-...@yandex.ru --- Themes can be distributed by distributions, but distributions usually do not have enough resources to maintain thousands of themes. That is why themes are usually distributed by authors in

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #9 from Martin Gräßlin --- > I wonder how the lookup is done in Metacity, Compiz, Openbox and XFWM which > are using the themes convention. honestly: I doubt they do. At least Metacity and Compiz have been dead for

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #10 from vladimir-...@yandex.ru --- > honestly: I doubt they do. What do you mean? -- You are receiving this mail because: You are the assignee for the bug. ___ Plasma-devel mailing list

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #11 from vladimir-...@yandex.ru --- > Openbox and XFWM are compared to KWin erm stagnating. I do not know about XFWM, but Openbox is just feature-complete and almost bug-free, so the term 'stagnating' hardly applies. It is being maintained

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #12 from Martin Gräßlin --- Sorry you misunderstood. My point is rather that KWin and those WMs are not comparable due to size of project. An openbox theme is not comparable to the theming KWin has in place, because

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #13 from vladimir-...@yandex.ru --- Kwin's complexity is understandable. But I suppose that it can still be boiled down to: 1. Something that renders (engine part) 2. Something that is being rendered (theme data part) Is that correct, or am

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #14 from Martin Gräßlin --- The problem with the proposed change is how we look up stuff. Currently we use an approach of one directory for a "theme element" and all themes install there. We can do a simple list of it.

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #15 from Sebastian Kügler --- You gave the answer yourself in the description, have another look at https://github.com/tsujan/Kvantum/commit/17a41413263dc546fac816ae1eb43aceb6366eb4 . If we added support for another path /

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

https://bugs.kde.org/show_bug.cgi?id=355906 --- Comment #16 from vladimir-...@yandex.ru --- Well, thanks for your response! If anyone has some input on theme handling in general or in specifics, please consider sharing it in this issue: https://github.com/lxde/lxqt/issues/572 -- You are