[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Breeze] [Bug 355906] Please consider unification for themes' data paths.
From:       via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date:       2015-11-26 14:37:19
Message-ID: bug-355906-17878-UUdLClimMv () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=355906

--- Comment #8 from vladimir-csp@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 distribution-independent ways.

Another example:
...GTK2 themes are data which is being shipped in $THEME_NAME/gtk-2.0. This
data is being used by GTK2 engine which is usually shipped by distribution.
(handful of engines, thousands of themes)
Example: Numix theme contains Numix/gtk-2.0 directory with data. It is used by
Murrine GTK2 engine which usually is already in distribution
(gtk2-engines-murrine in case of Debian). 

Theme author makes a theme named Foo which could include data for Plasma (svg
stuff), Qt5 Breeze engine (colors, images, whatever), Qtcurve (stylesheets)...
etc.

@Martin Gräßlin, I wonder how the lookup is done in Metacity, Compiz, Openbox
and XFWM which are using the themes convention.

> You reported this here in the breeze component.

Oh, sorry, my bad! I see, this caused some misunderstanding, and I did not
clarify why I picked Breeze. Well, I did it because I did not find a component
that would conceptually cover themes in general, but Breeze is the dominant
widget engine in KDE, so I picked it. Please reassign this request to a more
appropriate component. Please ask any questions if you want me to elaborate
something.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]