Search Criteria
Package Details: clearlooks-phenix-gtk-theme 7.0.1-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/clearlooks-phenix-gtk-theme.git (read-only, click to copy) |
---|---|
Package Base: | clearlooks-phenix-gtk-theme |
Description: | GTK3 theme visually close to Clearlooks |
Upstream URL: | https://github.com/jpfleury/clearlooks-phenix |
Keywords: | theme |
Licenses: | GPL3 |
Conflicts: | clearlooks-phenix-gtk-theme-git |
Submitter: | None |
Maintainer: | None |
Last Packager: | andreyv |
Votes: | 40 |
Popularity: | 0.000000 |
First Submitted: | 2013-04-10 08:52 (UTC) |
Last Updated: | 2022-08-09 07:33 (UTC) |
Dependencies (3)
- gtk-engines
- inkscape (inkscape-gitAUR) (make)
- mist-icon-themeAUR (optional) – a visually compatible icon theme
Latest Comments
1 2 3 Next › Last »
exploder-jimmy commented on 2022-08-09 20:06 (UTC)
@andreyv, Thank you!
andreyv commented on 2022-08-09 07:33 (UTC)
@exploder-jimmy Thanks, this should be fixed now.
exploder-jimmy commented on 2022-08-07 01:09 (UTC)
@andreyv, Please note that in process of building the icons from SVG sources
gtk-3.0/img/checkbox-checked.png
,gtk-3.0/img/checkbox-checked-hover.png
, andgtk-3.0/img/checkbox-checked-insensitive.png
images get lost for some reason.Though they are there in TAR archive before building.
Couldn't figure out the solution other than making copies from
*@2.png
ones afterwards.Like this:
andreyv commented on 2022-06-14 15:16 (UTC)
Thanks for the information, I'll look at the fork. Currently both Debian and Fedora packages of this theme still use the original upstream.
As an alternative, you can use the TraditionalOk theme from
mate-themes
, which is maintained and itself is a very old fork of this theme.MarsSeed commented on 2022-06-01 10:36 (UTC)
Seems this theme is EOL since 2016, but there is an up-to-date fork that purportedly works well with GTK 3.20+ and also with the GTK3 based Mate desktop:
https://github.com/jsane-h8ms/clearlooks-phenix.git
This fork includes the patches from other, earlier forks like keithbowes' one (though the GitHub fork 'Network' view does not show that, because the creator of the new fork cherry-picked the keithbowes patches manually).
There is no release tag (yet), but you can declare the source to point to a specific commit like this:
Latest commit: 2022-04-13 (abaffa3)
Be mindful that this version might or might not include the changes from your patches already, so it's best to verify if each of them is needed or not. If you do choose to migrate to the new fork, that is. :)
betruger72 commented on 2016-10-09 02:54 (UTC) (edited on 2016-10-09 03:16 (UTC) by betruger72)
andreyv commented on 2016-10-08 13:44 (UTC)
betruger72 commented on 2016-10-08 13:32 (UTC)
andreyv commented on 2016-10-07 15:15 (UTC)
1 2 3 Next › Last »