[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:07:36
Message-ID: bug-355906-17878-DQ6vTNyxPD () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #6 from vladimir-csp@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 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. for \
> instance themes of some things (Qt, KWin, GTK2, ...) are binary plugins, that can't \
> go in /usr/share as no binary libraries are allowed there.

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 data.

-- 
You are receiving this mail because:
You are watching all bug changes.


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