https://bugs.kde.org/show_bug.cgi?id=355906
Bug ID: 355906 Summary: Please consider unification for themes' data paths. Product: Breeze Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: plasma-devel@kde.org Reporter: vladimir-...@yandex.ru Hello everyone! There is an ongoing discussion in LXQt bugtracker about various themes and how to handle them. https://github.com/lxde/lxqt/issues/572 One of the issues is: theme data paths and naming. Some convention had formed, mostly in GTK world, but not limited to it, to place theme data into [$XDG_DATA_DIRS|$XDG_DATA_HOME]/$THEME_NAME/$COMPONENT, where $COMPONENT is the name of an engine, toolkit or application that is being themed by $THEME_NAME. "not limited to GTK" can be illustrated by the output of this command on my machine: $ ls /usr/share/themes/ | while read THEME ; do ls /usr/share/themes/"$THEME" ; done | sort | uniq cinnamon gnome-shell gtk-2.0 gtk-2.0-key gtk-3.0 metacity-1 openbox-3 Panel unity xfce-notify-4.0 xfwm4 (some non-related lines of output were excluded) This discussion has convinced tsujan (https://github.com/tsujan), developer of Kvantum Qt engine to add support of these paths in Kvantum (https://github.com/tsujan/Kvantum/commit/17a41413263dc546fac816ae1eb43aceb6366eb4). So, the list presented above may soon be supplemented with 'Kvantum' entry. I hope that this is a start of something very promising and would like to ask if you would agree to support this move in Qt theme engines of KDE. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel