Unico is a Gtk+ engine that aims to be the more complete yet powerful theming engine for Gtk+ 3.0 and newer. It’s the first Gtk+ engine written with Gtk+ style context APIs in mind, using CSS as first class citizen. Reproducible: Always
Created attachment 282047 [details] x11-themes/gtk3-engines-unico-0.1.0.74.ebuild Attached is an ebuild to install the unico engine for GTK+ 3.
gtk-3.1 is not going to be included in main tree for the time being. However this could be a nice addition to the gnome overlay.
(In reply to comment #2) gtk-engines-unico has been in the gnome-next branch of the gnome overlay (where all gnome-3.1.x packages go until gnome-3.0 is moved to portage) since mid-July. http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=tree;f=x11-themes/gtk-engines-unico;hb=refs/heads/gnome-next
I recently packaged unico, too. You can find it in the betagarden overlay, which is integrated into layman. You risk unstable glib and gtk3, though. if you pick x11-themes/light-themes, you get Ubuntu's look in addition.
Christoph, I just noticed the line sed -i -e "s:gtk_req, 3.1.6:gtk_req, 3.0.12:" configure.ac in the ebuild that you attached. Are you assuming it works because it compiles or have you made a in depth analysis?
I'm using unico with gnome 3.0 (form the overlay) for my everyday work (in fallback mode) and on my home system (gnome-shell). Compiles and works completely fine.
(In reply to comment #6) > I'm using unico with gnome 3.0 (form the overlay) for my everyday work (in > fallback mode) and on my home system (gnome-shell). Compiles and works > completely fine. Quoting the NEWS file for gtk+-3.1.6: * Many enhancements and fixes to CSS theming - The CSS parser has been rewritten with the goal of better CSS compliance and improved error handling - A testsuite for the parser has been added - Attributes can be inherited from parent widgets - Shorthand properties are supported - Color and font attributes are now inherited - Borders and padding are now handled much more consistently, and border-radius support is more complete - text-shadow, box-shadow and icon-shadow attributes are now supported - nth-child works for boxes In other words, that version of the unico engine might still compile, but due to massive changes in the behavior of gtk's CSS parser, on gtk+-3.0.x some themes rendered using unico will probably look rather different from what the theme designer intended.
Thanks for that research!
gtk-engines-unico-1.0.1 is now in portage, but is package.masked until gtk+-3.2 is unmasked.
(In reply to comment #9) > gtk-engines-unico-1.0.1 is now in portage, but is package.masked until gtk+-3.2 > is unmasked. In case you pull >=gtk+-3.1.6 into the tree before 3.2 -- unico would be happy with that, too
(In reply to comment #10) > (In reply to comment #9) > > gtk-engines-unico-1.0.1 is now in portage, but is package.masked until gtk+-3.2 > > is unmasked. > > In case you pull >=gtk+-3.1.6 into the tree before 3.2 -- unico would be happy > with that, too 3.1.6 is a development release of 3.2 and will not be added on top of 3.2. As in, 3.2 already is in-tree, but p.masked until some further review, whereas if 3.1.6 were in-tree, it would never ever exit p.masked status until purged out. You can add packages needing gtk-engines-unico to the tree p.masked, by adding the p.mask entry in the same block as that of gtk-engines-unico, and notify us, then we would unmask it for you together with gtk+-3.2, gtk-engines-unico and co soon (tm).
gtk+-3.2.1 and gtk-engines-unico are now unmasked.
