Package Details: xfce-theme-greybird 1.6.2-2

Git Clone URL: https://aur.archlinux.org/xfce-theme-greybird.git (read-only)
Package Base: xfce-theme-greybird
Description: A grey and blue Xfce theme, used by default in Xubuntu 12.04
Upstream URL: http://shimmerproject.org/projects/greybird/
Licenses: GPL, CCPL:by-sa-3.0
Groups: xfce-themes-shimmer-collection
Conflicts: xfce-theme-greybird-git
Submitter: flan_suse
Maintainer: bjo
Last Packager: bjo
Votes: 233
Popularity: 7.277265
First Submitted: 2011-02-02 15:41
Last Updated: 2015-09-09 16:34

Dependencies (7)

Required by (5)

Sources (1)

Latest Comments

emersonmx commented on 2016-04-15 15:22

Bye bye, greybird :'(
https://www.letras.mus.br/leandro-e-leonardo/197892/

grv commented on 2016-04-15 07:18

Bye bye, greybird :(

hikhvar commented on 2016-04-14 15:12

They want to fix. But they don't have time.
Quote from the Github Issue:

Yes, Greybird doesn't support Gtk+ 3.19 yet and since it will be a rewrite of the theme I guess I won't get to it very soon.
That said, if anyone wants to start working on that, that'd be appreciated!

grv commented on 2016-04-14 14:24

We need to convince them to fix it :)... It's my main theme :P

bjo commented on 2016-04-10 19:54

vertex looks also fine.

Punky commented on 2016-04-10 19:28

While waiting for resolve problem with gtk 3.20, we can use gtk-theme-arc....

bjo commented on 2016-04-10 10:33

Yep, according to https://github.com/shimmerproject/Greybird/issues/120 it will take some time to get the issues with GTK 3.20 fixed.

gray commented on 2016-04-10 10:17

Broken in GTK3 3.20.2 (works fine with 3.18). Haven't found updates yet.

sleeping commented on 2016-01-12 00:22

Hey guys, is this the same Greybird as the one from Xubuntu 14.40+?
This one looks a bit yellowish compared to that one;

Thanks!

Edit: yeah, [url=http://i1-news.softpedia-static.com/images/news2/Xubuntu-12-04-2-LTS-Is-Available-for-Download-Supports-UEFI-Secure-Boot-2.jpg]this[/url] is definitely not what it looks like on my computer.

It's a MacBook so the screen is reasonably good.
Any ideas how I can fix this?

EDIT2: I think my eyes just need adjustment and my screen could use some calibration. Very nice package!

petervaro commented on 2015-09-09 09:07

Symlink "xfwm4" in "/usr/share/themes/Greybird\ Compact" should be changed from:

"/usr/share/themes/Greybird/xfwm4_compact"

to

"/usr/share/themes/Greybird/xfwm4-compact"

bjo commented on 2015-09-09 06:24

Updated, will include the a11y-theme later.

Jristz commented on 2015-09-09 04:18

hellow greybird 1.6.2 is out with a new a11y xfwm4 theme

Spike29 commented on 2015-07-21 16:41

Hello, greybird 1.6 is out along with gtk3.16 support :)

hikhvar commented on 2015-04-22 12:30

Hey,

could you please add the fixes from this [1] Issue. Since the GTK3.16 Update I encounter also these black boxes.


[1] https://github.com/shimmerproject/Greybird/issues/84

bjo commented on 2015-01-21 10:59

Fixed.

4nduril commented on 2015-01-21 10:37

Is it possible that there is the wrong sha512 hash in the PKGBUILD? I get constantly "970ef8137d0e8ef44af171eeb6111f4c1ab09993f3dd3e5a2bc0dc9d731764f8d75be9d44f443feb06e5337c731d94280d2809c23405340f9539dbe86de9eeb7" while PKGBUILD says "5632dec64bbdaf0f8b3aa9654a56ed3f947c405fb1ded149c944394b641ba7354d10971519dddb44586300e7a1171ebf7dd549cbca49fd7caf44c8defb5f90f5"

bjo commented on 2015-01-18 22:29

Great, thanks :)

Spike29 commented on 2015-01-18 09:03

Hello, greybird 1.5.1 is out with gtk3.14 support :)

bjo commented on 2014-08-17 22:28

Thanks for the hint, updated :)

Spike29 commented on 2014-08-17 21:28

Hello, version 1.4.0 is out along with gtk3.12 support :)

bjo commented on 2014-06-05 13:42

Fixed.

bjo commented on 2014-06-05 13:37

Weird, it worked here. I'll take a look.

silvik commented on 2014-06-05 13:35

$ makepkg
==> Making package: xfce-theme-greybird 1.3.4-1 (Thu Jun 5 16:32:36 EEST 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
==> Extracting sources...
==> Entering fakeroot environment...
==> Starting package()...
cp: cannot stat ‘Greybird-1.3.4/’: No such file or directory
==> ERROR: A failure occurred in package().
Aborting...

hermes14 commented on 2014-06-05 13:35

There's no source=() in the PKGBUILD!

Spike29 commented on 2014-05-08 13:24

Here's an updated PKGBUILD for version 1.3.4 of the theme : http://pastebin.com/apxg5uTm

Can you please update ? :)

jazztickets commented on 2014-02-19 07:18

Hmm, now my incognito mode icon is brighter in chrome. Weird

Spike29 commented on 2014-02-16 16:39

Hello, greybird theme version 1.3.1 is out :)

jokeryu commented on 2014-02-14 15:37

optdepends lightdm-gtk-greeter should be lightdm-gtk2-greeter or lightdm-gtk3-greeter

lelele commented on 2013-12-27 19:08

For some reason chromium wasn't rendering the scrollbars right, this got me the fix. http://crunchbang.org/forums/viewtopic.php?pid=238076#p238076

bandroidx commented on 2013-10-18 15:29

anyone else having icon issues?

Anonymous comment on 2013-07-21 01:10

@thestinger - sorry about flagging, I'm new to Arch and AUR.

Anonymous comment on 2013-07-21 01:09

@thestinger - yes I'm aware of it but most new users will install this one first because it's linked from the Gerybird page and run into problems. I think it would save some users some time.

thestinger commented on 2013-07-21 01:08

please don't flag it out-of-date when there hasn't been a new upstream release

thestinger commented on 2013-07-21 01:07

@sirarch: there's an xfce-theme-greybird-git package

Anonymous comment on 2013-07-21 01:06

Could you please update the theme from GIT so it works better with GTK3? Thanks a lot for your work.

whizzo commented on 2013-05-25 05:17

fauno: Thanks

fauno commented on 2013-05-24 18:18

whizzo: use the git version

kolombo commented on 2013-05-14 09:01

Please don't remove classic theme :)

whizzo commented on 2013-05-13 07:57

Problems in gtk3 apps menus (transmission-gtk, file-roller,...)

luolimao commented on 2013-05-12 15:45

It seems like github is having issues with some of its repos atm: https://status.github.com/messages

twelveeighty commented on 2013-05-12 15:43

Hey @luolimao: thanks for picking up maintaining this package!

Is anyone else getting a "500 - Internal server error" on the https://github.com/shimmerproject/Greybird/archive/v1.1.1.tar.gz file?

luolimao commented on 2013-05-06 19:19

It was always there, but I can remove it if people find it to be a nuisance.

anonymous_user commented on 2013-05-06 04:50

Why was the classic theme added back in? Its not very compatible with the latest GTK3.

Tetsumaki commented on 2013-05-05 14:26

please use the git template in the abs package

check /usr/share/pacman/PKGBUILD-git.proto

flan_suse commented on 2013-05-04 13:11

I am disowning the Shimmer Project packages. luolimao will be adopting them.

Here is the complete list of Shimmer Project packages:

https://aur.archlinux.org/packages/elementary-xfce-icons/
https://aur.archlinux.org/packages/shimmer-wallpapers/
https://aur.archlinux.org/packages/xfce-theme-albatross/
https://aur.archlinux.org/packages/xfce-theme-blackbird/
https://aur.archlinux.org/packages/xfce-theme-bluebird/
https://aur.archlinux.org/packages/xfce-theme-greybird/

If you have any questions, don't be afraid to ask. But at this point, others probably know more than I do, since I haven't touched Arch Linux in a long time.

flan_suse commented on 2013-05-04 13:09

I am disowning the Shimmer Project packages. luolimao will be adopting them.

Here is the complete list of Shimmer Project packages:

https://aur.archlinux.org/packages/elementary-xfce-icons/
https://aur.archlinux.org/packages/xfce-theme-albatross/
https://aur.archlinux.org/packages/xfce-theme-blackbird/
https://aur.archlinux.org/packages/xfce-theme-bluebird/
https://aur.archlinux.org/packages/xfce-theme-greybird/

If you have any questions, don't be afraid to ask. But at this point, others probably know more than I do, since I haven't touched Arch Linux in a long time.

flan_suse commented on 2013-05-04 01:47

@bjo

"You were sick for 4 months? :p"

Hah, in a sense, I was "sick" from rolling releases for a long time. Not just Arch, either. I used to be a distro enthusiast, using 5 or more distros at once, constantly playing with them, learning new tricks, and having fun.

But as time passed, I need my computers to just get stuff done. I don't have as much time (or motivation) to keep maintaining a rolling release or playing around with distros.

It's too much hassle without much benefit for me.

In fact, I just tried updating my Arch system tonight, and it was hell. I mean, it's not even funny. I fixed one thing after the other, getting closer to achieving an updated system using the proper config files, but everytime I bump into a new hurdle. The forums show people with similar problems. I just gave up. I would have to start from scratch again, but I don't feel like it.

I have decided to disown the Shimmer Project packages, but I need to know who will adopt them? The PKGBUILDs are laid out in an organized manner with a lot of comments (hopefully this is helpful.) The only requirement I ask is that the new maintainer does not follow the git master branch. These should remain stable releases (e.g, 1.1, 1.2, 1.3, et al.) If you wish, you can make -git versions of each package.

Let me know, guys.

bjo commented on 2013-05-03 17:13

You were sick for 4 months? :p

flan_suse commented on 2013-05-03 13:22

Was sick and hadn't used my Arch Linux computer in a long time. (Getting tired of the issues with rolling releases.) I will have time tonight to update the Shimmer PKGBUILDs.

cmaloney commented on 2013-05-03 10:11

Current release is 1.1.1. Please update or disown.

wlmeng11 commented on 2013-04-28 17:34

Hi, can this theme be updated to be gtk3.8 compatible?

nuc commented on 2013-04-20 17:25

Why isn't the emerald theme integrated? It is in xfce-theme-greybird-git https://aur.archlinux.org/packages/xfce-theme-greybird-git/

I think it's missing in the PKGBUILD, the xfce-theme-greybird-git PKGBUILD says:
# install emerald theme
install -d -m 755 "$pkgdir"/usr/share/emerald/themes/Greybird
tar zxf Greybird.emerald -C "$pkgdir"/usr/share/emerald/themes/Greybird/

flan_suse commented on 2013-03-02 14:40

I think that's a good idea.

Not only did they drop support, but the rolling release nature of Arch Linux will not allow it, either.

I will update this and drop the classic theme. Sorry for those who have come to like the classic theme.

helmuthdu commented on 2013-03-02 14:03

I think you should remove the classic theme since it doesn't work on gnome and has no support.

Anonymous comment on 2013-02-20 06:37

Is awesome theme, perfect for xfce...

thanks

jyc commented on 2013-01-07 08:10

Thanks for the theme! :)

Anonymous comment on 2012-11-15 08:20

@ngaba, @flan_suse:

Thanks!

with patched gtk-engine-unico and adding:

GtkLabel, GtkLabel:active, GtkLabel:insensitive { background-color: transparent; }

to /usr/share/themes/Greybird Classic/gtk-3.0/gtk-widgets.css

everything seems work fine (as far as I can remember how it was before ;) )

http://kionez.org/unico-withoutpatch.png
http://kionez.org/unico-withpatch.png

ngaba commented on 2012-11-15 02:26

@kionez: Fortunately, this is an Unico bug, not Greybird Classic.

For a fix, try supersnail's patch:
https://bbs.archlinux.org/viewtopic.php?id=151817&p=1

flan_suse commented on 2012-11-03 13:15

@kionez

I just updated to gtk3 version 3.6.x on my Arch Linux machine (among other recent updates), and I feel that I might have to drop the Greybird Classic theme in this package. Not only is it no longer being maintained (in favor of the current vanilla theme), but it is slowly rotting away with each new major update to gtk3.

I preferred the classic theme myself (and it was the reason I was drawn to Greybird in the first place), but for practical reasons, I either must use the current Greybird theme or another Xfce theme. I'll likely just drop Greybird Classic in the next update of this PKGBUILD. This will also mean that the gtk-engine-unico package will no longer be required as an optdepends.

flan_suse commented on 2012-11-03 13:14

@kionez

I just updated to gtk3 version 3.6.x on my Arch Linux machine (among other recent updates), and I feel that I might have to drop the Greybird Classic theme in this package. Not only is it no longer being maintained (in favor of the current vanilla theme), but it is slowly rotting away with each new major update to gtk3.

I preferred the classic theme myself (and it was the reason I was drawn to Greybird in the first place), but for practical reasons, I either must use the current Greybird theme or another Xfce theme. I'll likely just drop Greybird Classic in the next update of this PKGBUILD.

Anonymous comment on 2012-11-02 16:36

@flan_suse
I do some tests, playing with gtk3's css but I don't find a decent solution for Classic style with new gtk3.. so, i try to switch to "vanilla" Greybird theme (I don't like it, but I can't find a good replacement). And about rolling-release distros: I'm coming from Gentoo.. I leave it because lately I have less spare time to keep everything togheter, so I understand your point of view ;)

Many thanks for your work!

flan_suse commented on 2012-11-02 11:22

@kionez

Sadly, the Shimmer Project dropped support for the classic Greybird theme. I'll see what I can do to fix the problem with your workaround. Lately, I've been using Arch Linux less and less because I'm getting tired of playing catch-up with the rolling-release train. I cross my fingers with every update, hoping that nothing will break or change drastically. On my "Arch Linux machine", I've actually been using Ubuntu 10.04 more often now. I'm still using a distro and packages from April 2010 (almost 3 years old) with less to worry about.

Anonymous comment on 2012-11-01 10:41

I'm trying to find wich update "breaks" the Classic flavour, there are also some changes in check buttons. I'm doing some RTFM for gtk-3's stylesheets, maybe I have to add some png in assets in order to have the "old" checkbutton style. I love the GreybirdClassic theme! :)

Anonymous comment on 2012-10-31 19:02

Using Greybird Classic, after some daily updates (mainly gtk3, I suppose) I have to add:

GtkLabel, GtkLabel:active, GtkLabel:insensitive { background-color: transparent; }

to /usr/share/themes/Greybird Classic/gtk-3.0/gtk-widgets.css because all labels are displayed in a wrong way (i.e.: with a light grey background), screwing up gtk3 applications (i.e.: networkmanager's nm-applet)

gtk3-demo-application with background-color:transparent --> http://kionez.org/gtk3-ok.png
gtk3-demo-application without background-color:transparent --> http://kionez.org/gtk3-no.png

Maybe it's not the right way to fix it, but hope it helps. :)

JoveYu commented on 2012-10-17 05:47

(gedit:3451): Gtk-WARNING **: Theme parsing error: gnome-applications.css:167:39: Missing closing bracket for pseudo-class

(gedit:3451): Gtk-WARNING **: Theme parsing error: granite-widgets.css:167:28: 'px' is not a valid color name

(gedit:3451): Gtk-WARNING **: Theme parsing error: lightdm-gtk-greeter.css:18:23: Horizontal and vertical offsets are required

(gedit:3451): Gtk-WARNING **: Theme parsing error: lightdm-gtk-greeter.css:38:23: Horizontal and vertical offsets are required

(gedit:3451): Gtk-WARNING **: Theme parsing error: lightdm-gtk-greeter.css:57:23: Horizontal and vertical offsets are required

flan_suse commented on 2012-09-25 21:10

The Shimmer Project released version 1.0.7 of Greybird.

Anonymous comment on 2012-09-18 12:35

@flans_suse yes, it does! Many thanks.

flan_suse commented on 2012-09-17 01:58

@ronsens and @akspecs

Does Greybird 1.0.6 fix this issue for you?

flan_suse commented on 2012-09-17 01:58

The Shimmer Project released version 1.0.6 of Greybird. It contains fixes for GTK2, GTK3, and Xfwm4.

flan_suse commented on 2012-09-14 18:00

@ronsens (and @akspecs)

I received an email from ronsens with the output of:

ls -l "/usr/share/themes/Greybird Compact/xfwm4/"

Everything checks out fine, permissions and files.

At this point, I am out of ideas why the xfwm4 theme is not displaying properly for you two. I can share some of my information, and maybe there's a difference with hardware that causes this:

Fully updated Arch, using Xfce 4.10
Using systemd + sysvinit mixed system
Intel video, i915 driver
Compositing is disabled
Grub options include: i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 pcie_aspm=force loglevel=3

flan_suse commented on 2012-09-14 17:59

@ronsens (and @akspecs)

I received an email from ronsens with the output of:

ls -l "/usr/share/themes/Greybird Compact/xfwm4/"

Everything checks out fine, permissions and files.

At this point, I am out of ideas why the xfwm4 theme is not displaying properly. I can share some of my information, and maybe there's a difference with hardware that causes this:

Fully updated Arch, using Xfce 4.10
Using systemd + sysvinit mixed system
Intel video, i915 driver
Compositing is disabled
Grub options include: i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 pcie_aspm=force loglevel=3

flan_suse commented on 2012-09-09 14:14

The Shimmer Project released version 1.0.4 of Greybird. It contains a minor fix for Mutter.

flan_suse commented on 2012-09-09 14:14

@ronsens and @akspecs

What happens if you type this command? Do you get a list of files?

ls -l "/usr/share/themes/Greybird Compact/xfwm4/"

flan_suse commented on 2012-09-08 23:03

@ronsens

I'm trying to reproduce the issue, but I am unable to. I even uninstalled and reinstalled 1.0.3 from scratch, yet I never have this problem. Do you by any chance have anything configured under $HOME/.themes/ ?

Anonymous comment on 2012-09-08 11:12

@flan_suse same issue here with compact classic windows decoration as described by @akspecs. I don't use the compositor and haven't used it before the last update, xfwm4 --replace has no effect. Please let me know if you need further information. Thanks!

flan_suse commented on 2012-09-07 11:52

@akspecs

This sounds like a random glitch you bumped into by random chance.

First try this. ALT + F2 and run: xfwm4 --replace

I am using the Greybird Compact xfwm4 with no issues, and the same is true if I switch to the regular Greybird xfwm4 theme. Are you using compositing by any chance? If so, does disabling compositing reveal the window decorations again?

flan_suse commented on 2012-09-07 11:51

@akspecs

This sounds like a random glitch you bumped into by random chance.

First try this: xfwm4 --replace

I am using the Greybird Compact xfwm4 with no issues, and the same is true if I switch to the regular Greybird xfwm4 theme. Are you using compositing by any chance? If so, does disabling compositing reveal the window decorations again?

flan_suse commented on 2012-09-07 11:49

@akspecs

I am using the Greybird Compact xfwm4 with no issues, and the same is true if I switch to the regular Greybird xfwm4 theme. Are you using compositing by any chance? If so, does disabling compositing reveal the window decorations again? What happens if run ALT + F2 and run: xfwm4 --replace

akspecs commented on 2012-09-07 08:41

I've pinpointed it to greybird compact specifically which is malfunctioning.

akspecs commented on 2012-09-07 08:39

After updating this theme it appears to be broken on my xfce desktop. I no longer have a bar above my windows, I cannot drag by clicking where it would normally be since it is not there. Though, it may be intersting to note that my close,minimize,roll-up,option buttons on this bar are still visible.

Any idea what might've broken something? Would it be possible for me to revert to the previous PKGBUILD? I don't have it.

flan_suse commented on 2012-08-31 16:25

The Shimmer Project released version 1.0.3 of Greybird. It contains some changes to the LightDM themes.

flan_suse commented on 2012-08-30 02:52

The Shimmer Project released version 1.0.2 of Greybird. The classic way of theming LightDM has been removed in favor of theming LightDM from within the "gtk-3.0/apps/" method. Fixes to GTK2, GTK3, and xfce4-notify have been published as well.

flan_suse commented on 2012-08-29 02:08

The Shimmer Project released version 1.0 of Greybird. Fixes and modifications have been made for the GTK3 and GTK2 themes. The classic theme is still included for the users to choose, since the new Greybird theme has a new blue look (0.9+) that appears very close to the traditional Clearlooks GTK theme, which some users do not prefer.

flan_suse commented on 2012-08-10 20:40

@dbdii407

Starting with version 0.9, gtk-engine-unico is no longer used (let alone required) by the GTK3 theme of Greybird. Only Greybird Classic requires it, which is an optdepends anyways.

For more information, read the email exchange between me and Simon below in the comments: https://aur.archlinux.org/packages.php?ID=46022&comments=all

The specific comment is Tue, 24 Jul 2012 03:29:04.

Here is a direct quote from Simon: "On the technical side, a lot has changed as well, partly this influenced more design decisions. Since there are plans upstream to deprecate the Unico-engine asap, we decided to get rid of it (and all the problems it introduced). So the Gtk3 theme was rewritten from scratch using only the default-engine and pure CSS, which also means it will work across more distributions and the Unico-version vs. Gtk3-version problems will disappear. The visual consequence were 'flat' buttons, because the default engine can't draw shadows outside a widget. However, I'm really happy with the new button style."

luolimao commented on 2012-08-10 19:23

The Greybird theme has 6 branches ("master", "gtk3.2", "gtk3.3", "gtk3.4", "gtk3.5", and "precise"). According to the README, only the "gtk3.2" branch needs the gtk-engine-unico dependency; the "master" branch, which this PKGBUILD uses, does not require it anymore. See the last 3 versions of the README for more info https://github.com/shimmerproject/Greybird/commits/master/README

Anonymous comment on 2012-08-10 17:18

Can you please add gtk-engine-unico to the dependency list? It's even mentioned in the README.

flan_suse commented on 2012-07-27 03:41

The Shimmer Project wallpapers now sit in their own separate package. The Greybird wallpaper is located in the shimmer-wallpapers package on the AUR. It is an optdepends.

Here is a list of Shimmer Project packages on the AUR; all Xfce-related:
* elementary-xfce-icons
* shimmer-wallpapers
* xfce-theme-albatross
* xfce-theme-blackbird
* xfce-theme-bluebird
* xfce-theme-greybird

flan_suse commented on 2012-07-26 19:34

@luolimao

"I'd rather not waste the space for the new Greybird."

"[...] and the people who use the classic theme probably wouldn't use the current theme. Of course, if there are people who do, they could just install both packages."

To respond to your first point: There's nothing I can really do about that, unfortunately. The classic Greybird theme (frozen at version 0.8.2) will not get any more updates / fixes. All the work will be done on the new "rich blue" Greybird theme. (See the email messages below for reference.) This is why I include both versions of this theme in the package; at least the user can decide which to use and switch back and forth between them. (I personally still use the classic theme, since that is what attracted me to Greybird in the first place. You know, Greybird, as in "grey"...) This method does not require extra bandwidth to build, and the extra space to have both versions of the theme installed is literally 123 KB.

To respond to your second point: It would be redundant to have separate packages for Greybird and Greybird Classic, just as it would be redundant to have separate packages for Greybird and Greybird Compact. The extra file space is only 123 KB anyways. However, to place the wallpapers in a separate package as an optdepends does seem to make sense, and it isn't really redundant. Plus, they reside on a separate GIT repository now, anyways.

I am going to make some updates again, sooner than later hopefully. Here is what to expect:

1) I will make a PKGBUILD named "shimmer-project-wallpapers" (or something like that) that will contain all of the Shimmer Project wallpapers, including any new ones in the future. (Albatross, Bluebird, Greybird, et al)

2) I will not include wallpapers with the themes anymore, since they will live in an optdepends under the package I described above.

3) Just like the elementary-xfce-icons, all of these packages will be under the umbrella *group of "xfce-themes-shimmer-collection". The icons and wallpapers will be optdepends of their respective themes.

4) gtk3 will continue to remain an optdepends for now.


Thanks for the feedback, everyone!


* I don't believe that any AUR helpers currently supports groups() right now, but I'll still use groups() for future purposes, just in case.

flan_suse commented on 2012-07-26 19:34

@luolimao

"I'd rather not waste the space for the new Greybird."

"[...] and the people who use the classic theme probably wouldn't use the current theme. Of course, if there are people who do, they could just install both packages."

To respond t oyour first point: There's nothing I can really do about that, unfortunately. The classic Greybird theme (frozen at version 0.8.2) will not get any more updates / fixes. All the work will be done on the new "rich blue" Greybird theme. (See the email messages below for reference.) This is why I include both versions of this theme in the package; at least the user can decide which to use and switch back and forth between them. (I personally still use the classic theme, since that is what attracted me to Greybird in the first place. You know, Greybird, as in "grey"...) This method does not require extra bandwidth to build, and the extra space to have both versions of the theme installed is literally 123 KB.

To respond to your second point: It would be redundant to have separate packages for Greybird and Greybird Classic, just as it would be redundant to have separate packages for Greybird and Greybird Compact. The extra file space is only 123 KB anyways. However, to place the wallpapers in a separate package as an optdepends does seem to make sense, and it isn't really redundant. Plus, they reside on a separate GIT repository now, anyways.

I am going to make some updates again, sooner than later hopefully. Here is what to expect:

1) I will make a PKGBUILD named "shimmer-project-wallpapers" (or something like that) that will contain all of the Shimmer Project wallpapers, including any new ones in the future. (Albatross, Bluebird, Greybird, et al)

2) I will not include wallpapers with the themes anymore, since they will live in an optdepends under the package I described above.

3) Just like the elementary-xfce-icons, all of these packages will be under the umbrella *group of "xfce-themes-shimmer-collection". The icons and wallpapers will be optdepends of their respective themes.

4) gtk3 will continue to remain an optdepends for now.


Thanks for the feedback, everyone!


* I don't believe that any AUR helpers currently supports groups() right now, but I'll still use groups() for future purposes, just in case.

flan_suse commented on 2012-07-26 19:27

@luolimao

"I'd rather not waste the space for the new Greybird."

There's nothing I can really do about that, unfortunately. The classic Greybird theme (frozen at version 0.8.2) will not get any more updates / fixes. All the work will be done on the new "rich blue" Greybird theme. (See the email messages below for reference.) This is why I include both versions of this theme in the package; at least the user can decide which to use and switch back and forth between them. (I personally still use the classic theme, since that is what attracted me to Greybird in the first place. You know, Greybird, as in "grey"...) This method does not require extra bandwidth to build, and the extra space to have both versions of the theme installed is literally 123 KB.

I am going to make some updates again, sooner than later hopefully. Here is what to expect:

1) I will make a PKGBUILD named "shimmer-project-wallpapers" (or something like that) that will contain all of the Shimmer Project wallpapers, including any new ones in the future. (Albatross, Bluebird, Greybird, et al)

2) I will not include wallpapers with the themes anymore, since they will live in an optdepends under the package I described above.

3) Just like the elementary-xfce-icons, all of these packages will be under the umbrella *group of "xfce-themes-shimmer-collection". The icons and wallpapers will be optdepends of their respective themes.

4) gtk3 will continue to remain an optdepends for now.


Thanks for the feedback, everyone!


* I don't believe that any AUR helpers currently supports groups() right now, but I'll still use groups() for future purposes, just in case.

flan_suse commented on 2012-07-26 19:26

@luolimao

"I'd rather not waste the space for the new Greybird."

There's nothing I can really do about that, unfortunately. The classic Greybird theme (frozen at version 0.8.2) will not get any more updates / fixes. All the work will be done on the new "rich blue" Greybird theme. (See the email messages below for reference.) This is why I include both versions of this theme in the package; at least the user can decide which to use and switch back and forth between them. (I personally still use the classic theme, since that is what attracted me to Greybird in the first place. You know, Greybird, as in "grey"...) This method does not require extra bandwidth to build, and the extra space to have both versions of the theme installed is literally 123 KB.

I am going to make some updates again, sooner than later hopefully. Here is what to expect:

1) I will make a PKGBUILD named "shimmer-project-wallpapers" (or something like that) that will contain all of the Shimmer Project wallpapers, including any new ones in the future. (Albatross, Bluebird, Greybird, et al)

2) I will not include wallpapers with the themes anymore, since they will live in an optdepends under the package I described above.

3) Just like the elementary-xfce-icons, all of these packages will be under the umbrella *group of "xfce-themes-shimmer-collection". The icons and wallpapers will be optdepends of their respective themes.

4) gtk3 will continue to remain an optdepends for now.


Thanks for the feedback everyone!


* I don't believe that any AUR helpers currently supports groups() right now, but I'll still use groups() for future purposes, just in case.

luolimao commented on 2012-07-26 18:20

That's just my point; I'd rather not waste the space for the new Greybird. And the wallpapers are too blue.

Anonymous comment on 2012-07-26 13:58

The new Greybird theme looks just like elementary, except with an uglier panel and fatter scroll bars.

If you're not using the Greybird Classic option, I recommend the elementary theme...

luolimao commented on 2012-07-26 04:18

I agree; I don't think it's necessary to add gtk3 as a dependency yet, since the gtk2 theme works just fine (although I do have gtk3 installed myself). Also, regarding the classic theme and wallpaper, I would personally prefer them in separate packages, since I don't think everyone would use the wallpaper (I for one don't), and the people who use the classic theme probably wouldn't use the current theme. Of course, if there are people who do, they could just install both packages. If you were to do package them separately (or if someone else did), you could stick the wallpaper in the optdeps.

Anonymous comment on 2012-07-26 04:09

thanx! about gtk3 dependency: leave as is. that's a better choice.

flan_suse commented on 2012-07-25 16:50

I have updated and modified the PKGBUILD.

This package will build and install the Greybird theme as well as the "classic" Greybird theme (version 0.8.2), without any conflicts or user intervention required. Everything, including the matching wallpaper, will remain intact.

If you bump into any issues or find any mistakes in the PKGBUILD, please let me know. I hope this works for everyone! I also included some shortcuts in the build() process to minimize bandwidth usage, thanks to the flexibility of GIT! Because of this reason, I will stick to using GIT for the build() process in the Shimmer Project stable releases (0.7, 0.8.0, 0.8.1, 0.8.2, 0.9, et al).

Enjoy!

P.S. To select the classic GTK theme, under Xfce go to Settings > Appearance > and choose "Greybird Classic" from the list. Since I do not yet use GTK3 applications, I am not sure how to do the same for the classic GTK3 theme; technically, it should be the same concept, since it resides under "/usr/share/themes/Greybird Classic/gtk-3.0" just like its classic GTK2 counterpart.

P.S.S. I am still contemplating whether or not I should add gtk3 as a dependency, or continue to leave it as an optdepends. Whatever works best for Arch users.

flan_suse commented on 2012-07-25 16:48

I have updated and modified the PKGBUILD.

This package will build and install the Greybird theme as well as the "classic" Greybird theme (version 0.8.2), without any conflicts or user intervention required. Everything, including the matching wallpaper, will remain intact.

If you bump into any issues or find any mistakes in the PKGBUILD, please let me know. I hope this works for everyone! I also included some shortcuts in the build() process to minimize bandwidth usage, thanks to the flexibility of GIT! Because of this reason, I will stick to using GIT for the build() process in the Shimmer Project stable releases (0.7, 0.8.0, 0.8.1, 0.8.2, 0.9, et al).

Enjoy!

P.S. To select the classic GTK theme, under Xfce go to Settings > Appearance > and choose "Greybird Classic" from the list. Since I do not yet use GTK3 applications, I am not sure how to do the same for the classic GTK3 theme; technically, it should be the same concept, since it resides under "/usr/share/themes/Greybird Classic/gtk-3.0" just like its classic GTK2 counterpart.

ork commented on 2012-07-24 20:49

Hello,

Not using Shimmer's wallpaper myself, I can't really comment on this subject.
As for the gtk themes, I like your approach to keep the package as upstream provides it while having a -classic one.

Thank you!

flan_suse commented on 2012-07-24 03:29

What follows is the email exchange between me and Simon. With his permission, I posted the entire discussion, with only minor editing. (I truncated some parts that were quoted in previous replies in order to make it more readable to the readers of this AUR comment.) Here is what I have decided to do, once I find the time to do so (hopefully soon):

1) I will likely switch to using the tarballs for the git-tag stable releases (0.7, 0.8.2, 0.9, et al).

2) I will continue to include the wallpapers with the packages, regardless of the fact that they now reside in a separate GIT repository.

3) For Greybird, I might use version 0.8.2 and its GTK2 and GTK3 themes, and rename them to "Greybird Classic". This way the user can choose "Greybird Classic" or "Greybird" (current stable release) under Xfce's Appearance settings.

Number 3 is because even though I disagree with the Shimmer Project's decision to use the new Greybird color scheme (rich, high-contrast blue that looks more blue than Bluebird itself), I want to maintain an Arch-like upstream mentality.

That concludes my own personal thoughts and ideas. Let me know what you think. As promised, here is the full email exchange between me and Simon:


--------------------


ME:

I noticed that the project has recently made some major changes to the GIT repository and Greybird theme.

1) By moving the wallpapers to their own separate repository, it makes packaging more difficult and inefficient. It requires the user to download more (xfce theme + all wallpapers, png and svg), and it causes conflicts with multiple GIT repositories (one for the theme, one for the wallpapers.) Also, it logically separates the themes from their wallpapers, which are still "parts" of the themes in the first place. I did a dirty workaround of wget'ing the wallpaper from the master branch of the Wallpapers repository. This is just a "workaround" and feels awkward, since the package is not building from a single location. It also means that any changes made to the wallpapers in the future will not reflect the version numbers of the git-tag releases for each theme. Can the wallpapers be moved back to their themes like before? You can still have a separate, un-versioned and un-tagged Wallpapers repository, but it would help to include *all* parts of the theme in a single repository (Albatross, Bluebird, Greybird, et al) like you've had since the beginning.

2) I noticed, as have others, that version 0.9 of the Greybird theme has changed drastically: it doesn't look like Greybird anymore. What used to be subtle grey hues are now rich blue; closer to what Bluebird is. The menu and highlight colors do not match the panel colors anymore, and it seems like this was a mistake? How come Greybird doesn't look like Greybird anymore? The other themes matured slowly, but didn't introduce any drastic changes in colors or consistency, so it was a surprise to see Greybird suddenly do this.

Let me know what you think, and thank you again!


--------------------


SIMON:

Hey!

> I noticed that the project has recently made some major changes [...]

Yes true, parts of it (also the visual changes) were announced on xubuntu.org

> 1) By moving the wallpapers [...]

The thing is that in Xubuntu (which atm is still the main target) the package "shimmer-themes" only contains the themes, not the wallpapers. Also: I personally don't associate the wallpapers with the themes at all. While making this connection might make more sense for Albatross and Bluebird (they both only had _one_ wallpaper), the wallpapers are in fact related to the Xubuntu releases only. (I'm not even the creator.)
Personally I think it was a mistake to throw them in the theme-repositories in the first place, so for me this is more the correction of a long-standing error than creating a new one.
From a user's perspective I'd like to think: why should I install a 2mb package if I just want a theme (that weighs a few kB).
Btw, this move was triggered by our Xubuntu packager complaining about the wallpapers being there :) (I guess I didn't care enough before.)

> 2) I noticed, as have others, that version 0.9 of the Greybird theme has changed drastically [...]

Yes, there were quite drastic changes and I expected far more negative feedback from the beginning. I could explain the rationale of each change if you like, for this email I'll leave you with the more obvious ones:
* bright menus: When playing with the theme more I once tried bright menus. Not only did that solve a lot of issues we were experiencing with icons, it also (subjectively, meanwhile: intersubjectively confirmed) made menus easier on the eyes. After using the bright menus for a few days I really didn't feel like going back. After a few discussions and rounds of gathering feedback (via IRC, Google+ mostly) I first pushed things to a "bright-menus" branch. Later as things started to get maturer, I decided (again, after discussion) to merge it.
* selected_bg_color: This was a consequence of the switch to bright menus. Simply put: the old highlight-color didn't work as well with the bright menus anymore, so I sought for a change. After testing and tweaking for a while, I decided to go with #398ee7 and even now (months later) I'm still happy with the choice.

On the technical side, a lot has changed as well, partly this influenced more design decisions. Since there are plans upstream to deprecate the Unico-engine asap, we decided to get rid of it (and all the problems it introduced). So the Gtk3 theme was rewritten from scratch using only the default-engine and pure CSS, which also means it will work across more distributions and the Unico-version vs. Gtk3-version problems will disappear.
The visual consequence were "flat" buttons, because the default engine can't draw shadows outside a widget. However, I'm really happy with the new button style.

All the best,
Simon

PS: If you want to be heard on issues like these _beforehand_, I'd like to invite you to one of our IRC channels (#shimmer and #xubuntu-devel on freenode.org).


--------------------


ME:

Thank you for the reply, and your explanation helps a lot. I'll see what I can do to workaround the new changes.

A few things I want to add / ask:

1) Would it be okay if I post this email exchange (I'll hide the addresses) in the comments page of the AUR? Rather than summarize what you've said, I can have your explanation be read in its entirety. If not, that's fine. I can just summarize it myself if you prefer this exchange to remain private.

2) I cannot idle in IRC channels as I have been able to in the past. If I have questions, I can try joining the channels and wait for a response for as long as I'm able to leave the laptop powered on.

3) The technical changes, such as using pure cross-compatible CSS will not affect packaging, so there's no worries there at all. It's the GIT structure that might make things tricky for me. I'll see what I can do to keep the package clean and efficient as before. I might even consider switching to the tarballs instead (e.g, v0.9 tar.gz), but that would remove the flexibility of GIT (allowing the user to comment out certain lines to use the master branch instead of the stable git-tag release.) Either way, I only follow the stable git-tag release versions, for reasons I've explained in the past.

Thank you again for you reply, Simon! All the best!


--------------------


SIMON:

> Thank you for the reply [...]

Good to read!

> A few things I want to add / ask:

> 1) Would it be okay if I post this email exchange [...]

Sure, feel free to post it. I never managed to write the comprehensive blog post about these changes that I'd have wished to. But well, not enough time/energy for everything...

> 2) I cannot idle in IRC channels as I have been able to in the past [...]

Fine, no problem. Was more meant as an offer. ;)

> 3) The technical changes, such as using pure cross-compatible CSS will not affect packaging [...]

Feel free to drop the wallpapers from your package as well, I'm afraid there's not much more I can suggest...

> Thank you again for you reply [...]

You're welcome - thanks for your packaging efforts!


--------------------


This ends the email exchange.

flan_suse commented on 2012-07-23 14:24

@ork

I emailed them about these sudden changes (colors don't match anymore and GIT repositories changed). I'll write a comment in here if I find out anything. I think the new menu appearance is inconsistent, and I'm not sure why it was changed so drastically.

ork commented on 2012-07-23 07:46

Does anyone have a patch that reverts menus appeareance like in previous versions ? They look like before in the Blackbird theme, so I did a quick patch for the gtk2 theme (http://pastebin.archlinux.fr/449072) but I can't figure out how to do it for gtk3.

flan_suse commented on 2012-07-23 03:17

The Shimmer Project released version 0.9 of Greybird. It introduces Unity-specific additions, and includes some polishing up of the GTK2 and GTK3 themes.

The Shimmer Project has moved their wallpapers to a separate GIT repository, which complicates the package building process a bit. If I included both repositories (theme and wallpapers), it would require all wallpapers to download, plus the conflicts with the different GIT repositories is a hassle. So for now, I decided to just wget the specific wallpaper file. I may contact the Shimmer Project and see if they can return to the traditional approach of including the wallpapers in the same repository as each theme. Not only is packaging cleaner, easier, and more organized; but a theme should always have its wallpaper as part of the theme in its entirety. There is no need to separate them.

Comment if you have questions, issues, corrections, or suggestions.

flan_suse commented on 2012-07-09 03:02

Made the fixes to all the PKGBUILDs. Packages still build properly, like before, but hey, a typo's a typo.

luolimao commented on 2012-07-07 16:39

@flan_suse
Didn't think to check the githubs themselves. My bad. Anyway, according to the Blackbird github, that's dual-licensed too; evidently, your licensing was correct for all four packages. They probably just forgot to add the license files in (seeing as LINCENSE.GPL isn't there either). Anyway, regarding the $srcidr thing, it's just cd'ing to nowhere, since $srcidr would be empty. By default it's already in $startdir (usually - but not always - one directory up from $srcdir) so it dumps everything there. At least everything works out in package() regardless :]
Anyway, thanks for packaging this. It's really a complete and nice-looking theme.

flan_suse commented on 2012-07-07 12:02

@luolimao

Nice catch on the typo! I'm curious as to why it doesn't spit out an error in the very first step of the build() process? I will fix that typo in all the PKGBUILDs as soon as I get the chance. Thankfully, the packages have all been working, regardless.

As for the licenses, the CCPL applies to the wallpapers, not the code itself. Since Bluebird and Greybird also include wallpapers by the Shimmer Project, I went ahead and assumed they use the same license as for their Albatross wallpaper. If you look in the github repositories, you will see LICENSE.CC in all of their Xfce themes, except for Blackbird. I left CCPL in Blackbird by mistake, but didn't yet update the PKGBUILD. (Not a high priority to require a package rebuild; just a minor technicality.)

luolimao commented on 2012-07-07 05:30

I believe there's a typo in the build() section (should be $srcdir, not $srcidr), and the typo is in all the related packages (xfce-theme-{bluebird,blackbird,albatross}) . Also, (minor nitpicking, I know) the Albatross theme does have a double-license (CCPL:cc-by-sa-3.0 and GPL3) but according to the site link, the Bluebird and Greybird themes are GPL3 only (and so would Blackbird, I assume).

flan_suse commented on 2012-05-28 02:56

The Shimmer Project released version 0.8.2 of Greybird. It includes some minor fixes throughout, as well as a new logout dialogue theme. The logout dialogue is darker and resembles the new (young) Blackbird theme.

Thanks to the suggestion of thestinger, I have rewritten this PKGBUILD so that it can be built and rebuilt over and over without any git errors. Check the PKGBUILD if you are curious. Please report any problems.

I will hopefully soon make the same changes to my other PKGBUILDs of the Shimmer Project Xfce themes.

flan_suse commented on 2012-05-28 02:42

Thanks to the suggestion of thestinger, I have rewritten this PKGBUILD so that it can be built and rebuilt over and over without any git errors. Check the PKGBUILD if you are curious. Please report any problems.

I will hopefully soon make the same changes to my other PKGBUILDs of the Shimmer Project Xfce themes.

flan_suse commented on 2012-05-28 02:39

Thanks to the suggestion of thestinger, I have rewritten this PKGBUILD so that is can be built and rebuilt over and over without any git errors. Check the PKGBUILD if you are curious. Please report any problems.

I will hopefully soon make the same changes to my other PKGBUILDs of the Shimmer Project Xfce themes.

flan_suse commented on 2012-05-28 02:38

Thanks to the suggestion of thestinger, I have rewritten this PKGBUILD so that is can be built and rebuilt over and over without any git errors. Check the PKGBUILD if you are curious.

flan_suse commented on 2012-05-28 02:36

The Shimmer Project released version 0.8.2 of Greybird. It includes some minor fixes throughout.

flan_suse commented on 2012-05-16 21:54

@thestinger

Before I upload any changes, how does this look: http://pastebin.com/gLhRqaFf

It builds the package correctly, even with subsequent builds. However, this makes things a bit more complicated than they previously were. I even had to use different aliases at the top, since using the official _gitroot and _gitname overwrites the PKGBUILD with an updated pkgver number (against my wishes.) This is, after all, not a -git package, but a stable release. I just use git in the PKGBUILD because it is more flexible (users can use the master branch or any branch of their choice), and there were random server issues with the tarballs on their github in the past.

Let me know what you think. I will also make the same changes to my other Shimmer Project PKGBUILDs.

thestinger commented on 2012-05-16 02:34

@flan_suse: in build(), you should do the clone like it's done in /usr/share/pacman/PKGBUILD-git.proto, which won't have to re-fetch the sources if you're just rebuilding and will just fetch deltas on an update if you've kept the package sources around. You can skip making a "$srcdir/$_gitname-build" directory though because you don't need to build anything.

In package(), replace the clone with copying over the git repository from "$srcdir" and leave the rest as it is or just copy over the files that are needed (either works).

thestinger commented on 2012-05-16 02:33

@flan_suse: in build(), you should do the clone like it's done in /usr/share/pacman/PKGBUILD-git.proto, which won't have to re-fetch the sources if you're just rebuilding and will just fetch deltas on an update if you've kept the package sources around. You can skip making a "$srcdir/$_gitname-build" directory though because you don't need to build anything.

In package(), replace the clone with copying over the git repository from "$srcdir" and leave the rest as it is.

flan_suse commented on 2012-05-16 01:49

@thestinger

I'll try that out tomorrow if I have the free time. It makes sense from how you've described it. I just always viewed build() to be reserved for actual compiling, and I never considered pulling from a git repository to fall under the compile/build category. "...so the package can be rebuilt (or just repackaged) without fetching the source again." I never knew that it made a different when using git. So you mean to say that if I place the git clone and checkout in build(), any subsequent runs of makepkg will skip this part? Not sure if I interpreted it 100%.


@Math

In the meantime, let me know if yaourt works (even with multiple builds), since I just tried it out with no issues. When I test my PKGBUILDs with makepkg, I always start with a clean build directory.

thestinger commented on 2012-05-15 19:09

@flan_suse: you should use a separate build directory like the prototype PKGBUILDs though (/usr/share/pacman).

The clone (and probably the checkout too) belong in a build() function (checking out to "$srcdir") and then copying to "$pkgdir" in package() so the package can be rebuilt (or just repackaged) without fetching the source again.

Anonymous comment on 2012-05-15 19:04

@flan_suse

Thnx for your reply.
I'm just using makepkg, but I'll see what yaourt can do for me. :)

flan_suse commented on 2012-05-14 23:43

@Math

How are you building the package? Are you using a helper (e.g, yaourt), or are you manually using makepkg? Yaourt automatically starts with a clean build directory, so I never get such a problem.

Anonymous comment on 2012-05-14 19:12

I'm getting this error:

error: Your local changes to the following files would be overwritten by checkout:
README
gtk-2.0/gtkrc
gtk-3.0/gtk-widgets.css
gtk-3.0/gtk.css
metacity-1/metacity-theme-1.xml
Please, commit your changes or stash them before you can switch branches.

Not sure what to do, maybe someone can help.

flan_suse commented on 2012-05-03 19:57

@txus

I tried out LightDM (lightdm-gtk-greeter), and I got it to work with the below steps to use the Greybird theme and wallpaper. It looks nice, and it's not too cluttered. It also looks much better than GDM, that's for sure.

I bumped into some problems:
* For some reason it requires accountsservice and libsystemd. ("Light" DM, eh?)
* Because of this, it ignores the users.conf options, and it displays the "lightdm" user in the login list.
* The buttons on the upper-right (accessibility and power) are buggy. Sometimes they are delayed, and sometimes you must click them repeatedly to display the drop-down options. (Might only be a bug with lightdm-gtk-greeter, though.)
* The "Computer" icon has no easily discoverable way to change it. I found out how to, in the Wiki page, and I changed it to an Arch logo. (Could have been easier.)

All in all, LightDM seems to be useable, and it looks great with the Greybird theme and wallpaper! Would be interesting to play around with the other greeters, such as lightdm-unity-greeter. For now, though, I am switching back to XDM and the Arch XDM theme. I don't doubt this login manager will improve with time, especially since it is the default for Ubuntu and Xubuntu.

flan_suse commented on 2012-05-03 15:16

If you use LightDM and wish to use the Greybird LightDM theme, just make the following changes to your /etc/lightdm/lightdm-gtk-greeter.conf file like so:

[greeter]
background=/usr/share/xfce4/backdrops/Greybird.png
theme-name=Greybird LightDM
icon-name=elementary-xfce-dark

The icon-name line should only be used if you installed the elementary-xfce-icons package: https://aur.archlinux.org/packages.php?ID=58598

flan_suse commented on 2012-05-03 13:51

If you use LightDM and wish to use the Greybird LightDM theme, just make the following changes to your /etc/lightdm/lightdm-gtk-greeter.conf file like so:

[greeter]
background=/usr/share/xfce4/backdrops/Greybird.png
theme-name=Greybird LightDM
icon-name=elementary-xfce-dark

flan_suse commented on 2012-05-03 13:50

Thank you for the response. I may give LightDM a try sometime. By viewing your lightdm-gtk-greeter.conf file, I better understand how it works. I'm going to add an extra comment to explain it to others who might read these comments.

Anonymous comment on 2012-05-03 08:40

Sorry for the late answer, I had an exam this morning. Ok, now it works great. Thanks!

About my configs, actually my lightdm.conf is the default one, and I have only customized lightdm-gtk-greeter.conf. Here it is: http://pastebin.com/yNRNr7N0. To start it, I use it as a daemon in rc.conf, just add lightdm to the array :). By default it reads and starts the sessions from /usr/share/xsessions with an already provided script, but there was a big discussion recently on the aur comments about how it should or shouldn't work. Bottom line is, you can customize it to your liking e.g. just by writing your own script and changing "session-wrapper" in lightdm.conf, but by default it "just works"(tm) for starting DE sessions. That said, personally I haven't tried customising it. And as I said before, I'm by no means an expert!

And thanks for explaining about the PKGBUILD!

flan_suse commented on 2012-05-03 01:57

I made the change in the PKGBUILD. Let me know if this works.

flan_suse commented on 2012-05-02 16:52

@txus

Oops! That "gtk3" thing was a typo! I will make the correct change tonight after work. In the meantime, I would love to see your config files for lightdm.conf, lightdm-gtk-greeter.conf, and inittab (or whichever method you use to start the display manager.)

I may try to play around with LightDM myself, just to get a better idea. Of course, it's better to use pastebin.com, rather than dumping them directly in the comments here.

As for switching to LightDM, where does it read your login sessions (Xfce, GNOME, KDE) from? My current XDM setup simply reads a file in my home folder that runs startxfce4. It appears that everyone has a different idea of how to start a session, and even with our "standards compliant" philosophy, the reality is far from it. (Just look at how each desktop environment/distro handles the default web browser configuration! It's insane.)

As for "optdepends", yes, if the dependency is not required to run/install the package, it should be an optdepends. Other distros call these "recommended" or "suggested" dependencies; Arch Linux calls them "optdepends".

In this case, not everyone uses/installs gtk3 or lightdm, and they are not required to use the Greybird theme. However, those who wish to use the gtk3 theme or the lightdm theme do require the optdepends: gtk-engine-unico and lightdm-gtk-greeter. The Elementary Xfce icons ae not required either, but they are a matching icon set that goes well with the theme, so it is also an optdepends.

flan_suse commented on 2012-05-02 16:48

@txus

Oops! That "gtk3" thing was a typo! I will make the correct change tonight after work. In the meantime, I would love to see your config files for lightdm.conf, lightdm-gtk-greeter.conf, and inittab (or whichever method you use to start the display manager.)

I may try to play around with LightDM myself, just to get a better idea. Of course, it's better to use pastebin.com, rather than dumping them directly in the comments here.

As for switching to LightDM, where does it read your login sessions (Xfce, GNOME, KDE) from? My current XDM setup simply reads a file in my home folder that runs startxfce4. It appears that everyone has a different idea of how to start a session, and even with our "standards compliant" philosophy, the reality is far from it. (Just look at how each desktop environment/distro handles the default web browser configuration! It's insane.)

Anonymous comment on 2012-05-02 16:24

<offtopic> Lightdm
Well, I'm no expert at all, but roughly it's a bit simpler.

Lightdm needs a greeter to work, which is the actual "login screen", but it doesn't matter if it is the GTK one, Unity, or whatever. They are independent, so you don't need one to make the other work, as far as I know. It's configured using .conf files, not dconf (at least the gtk greeter). And yeah, you change the icons in the same way you change the theme or the font, just by naming it, and you can also specify an image or color as background.

To configure it just follow the article in the arch wiki. Roughly, install lightdm and lightdm-gtk-greeter from aur, edit /etc/lightdm/lightdm-gtk-greeter.conf to your liking (and also have a look at lightdm.conf in the same directory, just for fun), and make it start at boot. That's it, basically. And no, I don't have the unity greeter (although it looks pretty smooth, maybe i'll try it sometime :) ). As I said before, the greeters are independent from each other.

And of course, I use the superb XFCE :D If you want any of my configs, you're welcome to ask!
</offtopic>

About the changes, you have to link to "gtk-3.0", not "gtk3". That's the standard directory for a gtk3 theme (which is actually everything there is to the lightdm theme, it's just a dark gtk3 theme).

And I don't know much about PKGBUILD policies, but in regard to the optdepends line it's not like you actually "need" lightdm-gtk-greeter to use the theme, but more like "if you install it, we have this special theme for it besides our standard one". Is it correct to put it in optdepends? I'm asking out of ignorance, really lol

And BTW, sorry for not saying this earlier.. Thank you for writing this aur package! :)

flan_suse commented on 2012-05-02 13:33

@txus

I made the changes to the PKGBUILD, but I haven't tested it myself. Upon further inspection, LightDM has confused me even more. I can't tell if you must configure it with a .conf file or with dconf. I am having secound thoughts about lightdm-gtk-greeter, since Greybird may require lightdm-unity-greeter (heavy ties to Xubuntu, and it would require a lot of extra dependencies.) I'm not even sure if you change the LightDM background in the same way you change its theme in the same way you change the icons.

Can you share the steps you took to changing your LightDM theme, background, and icons? What packages do you have installed? Only lightdm? Do you have lightdm-gtk-greeter? Do you have lightdm-unity-greeter? Are you using Xfce or Unity?

Anonymous comment on 2012-05-02 07:34

Don't worry, I'll test it and tell you how it goes. I know lightdm is still a bit "green", not at all mature, and still changing, but it will get there :) And are you sure you must add lightdm-gtk-greeter as optdepends? You're the master, I don't know how to write PKGBUILDs properly.

About the linking, last time I tried to do it the way you say it didn't work, apparently it needs a ${theme_name}/gtk-3.0/ kind of directory structure (it reads standard gtk 3.0 config).

flan_suse commented on 2012-05-02 04:07

@txus

I don't use LightDM, myself, so I won't be able to test any changes. I am not entirely sure where LightDM themes should be placed, and how LightDM reads them. From what I can gather, lightdm requires a greeter (in this case it is lightdm-gtk-greeter?), which relies on gtk3 to be installed as a dependency.

I will see if I can make the changes to the PKGBUILD tomorrow if I have time, but I will not be able to test it myself, since I use XDM, not LightDM. (The state of LightDM under Arch Linux seems a bit unready at this point.) I do know I must add lightdm-gtk-greeter as an optdepends when I modify the PKGBUILD.

Why must the "Greybird LightDM/gtk-3.0" directory link to the "Greybird/lightdm" directory? Why can't the user tell the LightDM greeter to point to "/usr/share/Greybird/lightdm/" as the theme?

Anonymous comment on 2012-05-01 23:17

Not extactly, sorry for not expressing it correctly. There is a specific gtk3.0 theme for the gtk greeter of lightdm. This is not accessible by default, but a simple link like the one for the compact version of xfwm gives you the option to use it. In the PKGBUILD it could be sth. like this (shameless quick mod of what lowph posted already):

# Make a symbolic for Greybird Lightdm
mkdir -p "${pkgdir}/usr/share/themes/${_pkgname} Lightdm"
ln -s "../${_pkgname}/lightdm" "${pkgdir}/usr/share/themes/${_pkgname} Lightdm/gtk-3.0"

flan_suse commented on 2012-04-30 14:18

@txus

What do you mean? I don't think I understood the question. Do you mean there is a "compact" version of the lightdm theme as well?

Anonymous comment on 2012-04-30 09:07

Could you do the same for the lightdm theme? It works exactly the same way. Thanks!

Jristz commented on 2012-04-30 07:40

the new location for xfce background is /usr/share/backgrounds/xfce
put Greybird.png in /usr/share/backgrounds make the system mistake the path and not show wallpaper in backgrounds/xfce I not sure if only in my system or is on other system

any can onfirm or not this?

lowph commented on 2012-04-29 15:20

Thanks, it's working fine.

flan_suse commented on 2012-04-29 03:02

I updated the PKGBUILD to include and install the "compact" version of the Greybird xfwm4 theme, thanks to the comment and assistance from lowph. It is named "Greybird Compact", and it uses up less space, which can be helpful for smaller screens and netbooks.

I made some modifications so that it sticks to a more standard PKGBUILD approach. Let me know if there are any issues. Enjoy!

flan_suse commented on 2012-04-29 03:00

I updated the PKGBUILD to include and install the "compact" version of the Greybird xfwm4 theme, thanks to the comment and assistance from lowph. It is named "Greybird Compact", and it is uses up less space, which can be helpful for smaller screens and netbooks.

I made some modifications so that it sticks to a more standard PKGBUILD approach. Let me know if there are any issues. Enjoy!

flan_suse commented on 2012-04-28 23:23

@lowph

Sure thing. I was thinking of doing something similar before, but held off on it. I can do it tonight. I would right now, however I want to have enough time to test it myself and make sure it works properly with no conflicts or unintended issues. I am a little busy at the current moment.

I shall do this tonight before I go to sleep.

Good suggestion, and thanks!

lowph commented on 2012-04-28 15:49

Can you make Greybird-compact available by adding the change below?
At end of package()

# Make a symbolic for Greybird-compact
mkdir -p "${pkgdir}/usr/share/themes/${_pkgname}-compact"
ln -s "../${_pkgname}/xfwm4_compact" "${pkgdir}/usr/share/themes/${_pkgname}-compact/xfwm4"

flan_suse commented on 2012-04-26 19:56

The Shimmer Project released version 0.8.1 of Greybird. It adds more touches for Unity support.

Nierro commented on 2012-04-24 09:11

Ok, i was using the battery-applet instead of the icon from xfce4-power-manager, i'm an id..t!
Thanks for your help and sorry for the waste of time...

Nierro commented on 2012-04-24 09:00

xfce4-battery-plugin 1.0.1... so it is really strange problem, because i tried cbatticon from aur, and it has the right icon.
But i want to use my xfce-battery-plugin. Weird to hear your plugin is called xfce4-power-manager... i have not an applet with that name!

Nierro commented on 2012-04-24 08:37

can you please tell me what does your /usr/share/xfce4/panel/plugins/battery.desktop "icon" line contain? I think that is the problem.

Nierro commented on 2012-04-24 08:26

Uhm i found out i've got no /usr/share/xfce4/panel-plugins/xfce-battery-monitor.desktop ... I tried to install it again, but nothing change. Is it normal?

Nierro commented on 2012-04-24 08:18

xfce4-battery-plugin 1.0.1... so it is really strange problem, because i tried cbatticon from aur, and it has the right icon.
But i want to use my xfce-battery-plugin.

flan_suse commented on 2012-04-23 22:01

@Nierro

The issue is not with the Greybird theme, but it is either due to the icon theme or the battery applet. I think it is the battery applet, since when I change my icon theme (such as Elementary Xfce Dark), it correctly changes the battery icon.

Right-click on your battery icon and go to About. What does it say? It should say "xfce4-power-manager". If not, then it appears that you are using a different power/battery applet.

Nierro commented on 2012-04-23 18:29

ok, here is the screen...i've already logout and login!
http://img708.imageshack.us/img708/8486/istantanea2304201220270.png

Nierro commented on 2012-04-23 18:22

well, sorry then...and thank you very much for your patience!

flan_suse commented on 2012-04-23 18:03

@Nierro

I made a comment in this PKGBUILD page: https://aur.archlinux.org/packages.php?ID=58598

Sometimes you must logout and login again, or reload the Xfce panel for the new icons to be used. Can you link to a screenshot of which battery icon is being used?

As for the .gtkrc-2.0, that problem is common, since some users do have customizations in their home directory. If you look at all of the comments, you will see that someone else had the same issue, until they removed the file from their home folder.

Nierro commented on 2012-04-23 17:55

Ok, i deleted my .gtkrc-2.0 in my home folder, and then after logout and login, everything is themed.
Now only battery applet won't get themed...it remains the same although i've seen in the folder /usr/share/icons/elementary-xfce-icons that there are battery icons...i can't understand why!

Nierro commented on 2012-04-23 17:54

Ok, i deleted my .gtkrc-2.0 in my home folder, and then after logout and login, everything is themed.
Now only battery applet won't get themed...it remains the same although i've seen in the folder /usr/share/icons/elementary-xfce-icons that there are battery icons...i can't understa

flan_suse commented on 2012-04-23 17:10

@Nierro

Could you rephrase that? I am not sure I fully understand what you've said. I noticed that with any Xfce theme I apply, I must restart/reload the panel in order to have it themed properly. The same thing works if you logout and login again. (This happens for any theme and icon set.)

In my case, selecting Greybird as my theme properly changes the panel to use the correct theme when I reload the panel. So this means it is correctly reading panel.rc in the line "include apps/panel.rc".

Unlike with GNOME, Xfce does not seem to update the panel automatically upon selecting a new theme or icon set. The same is true when changing the mouse cursor under Xfce; the xfwm4 window manager must be restarted.

Nierro commented on 2012-04-23 15:11

The lines in /usr/share/themes/Greybird/gtk-2.0/gtkrc
# panel theming
include "apps/panel.rc"
Does not include that file, if i want to, i have to manually had to add widget
"*Xfce*Panel*" style "theme-panel" to gktrc.
In this way, panel applets will change if i change icon theme, and the panel itself gets themed.
Is this my problem? Running xfce 4.8.
Thanks

flan_suse commented on 2012-04-18 15:11

The Shimmer Project released version 0.8 of Greybird. It includes a fix for Unity, in preparation for the release of Ubuntu 12.04.

Nierro commented on 2012-04-11 07:28

Yes, i knew, this is why i was talking about news! ;)
Thanks for the quick answer, hope they'll become soon themeable!

flan_suse commented on 2012-04-10 23:18

@Nierro

Last I heard from the Shimmer Project, Chromium's scrollbars are not themeable. At least not yet.

Nierro commented on 2012-04-10 20:19

news about chromium scrollbars support?

flan_suse commented on 2012-03-29 02:16

The Shimmer Project released version 0.7.1 of Greybird. It includes a small change in its GTK3 theme.

flan_suse commented on 2012-03-22 03:25

The Shimmer Project released version 0.7 of Greybird. It includes minor fixes.

flan_suse commented on 2012-03-14 00:21

The Shimmer Project released version 0.6 of Greybird.

Since this was a quick release, I did not make gtk-engine-unico a strict "depends" yet. See below if you want to understand my dilemma.

flan_suse commented on 2012-03-06 18:02

The Shimmer Project released version 0.5 of Greybird. It comes with both GTK2 and GTK3 fixes.

Should I make gtk-engine-unico a depends, or leave it as an optdepends? GTK3 applications are slowly but surely replacing GTK2. Sadly, gtk-engine-unico is only available through the AUR, as it hasn't yet been adopted on the Community repository. Changing it from an optdepends to a depends would mean that users of xfce-theme-greybird would automatically pull in the gtk3 package. Not sure how light some people prefer to keep their systems, so I may leave it as an optdepends for now. Later, I might have to just go ahead and change it to a legitimate dependency in light of the pace GTK3 is spreading.

flan_suse commented on 2012-03-06 17:58

The Shimmer Project released version 0.5 of Greybird. It comes with both GTK2 and GTK3 fixes.

Should I make gtk-engine-unico a depends, or leave it as an optdepends? GTK3 applications are slowly but surely replacing GTK2.

flan_suse commented on 2012-02-04 04:22

The Shimmer Project released version 0.4 of Greybird four days ago. It comes with bugfixes throughout the theme, including GTK3 fixes.

flan_suse commented on 2012-01-23 15:04

@unhammer

That's true. Any customizations or changes written in ~/.gtkrc2.0 will override the global theme. While this can cause conflicts, it can also be used to tweak a personal theme without having to mess with any global files. Such an example is enabling the Nautilus "breadcrumbs" location bar with the proper files and modifications to ~/gtkrc-2.0.

unhammer commented on 2012-01-22 12:47

ah, fixed it myself, had to delete ~/.gtkrc-2.0* :)

unhammer commented on 2012-01-21 20:56

I get this fugliness: http://bildr.no/image/1085088.jpeg
(installed both optdepends, didn't help, did select greybird in both Appearance and Window Manager …)

flan_suse commented on 2011-11-26 15:43

@Diaz

"I don't rememberever changing any style for firefox so i think this is how it looks by default..."

That's exactly how it looks for me as well. From what I understand, Firefox's interface is written in XUL, which draws in GTK for the Linux platform. It's not native GTK like Epiphany, Thunar, Evince, GIMP, Nautilus, and all the other applications commonly found in GNOME or Xfce.

I do not know if this can be fixed from the themer's end. You can try asking in the Shimmer page (linked in the description), but I wouldn't get my hopes up. This is simply how Firefox's GUI is built.

Diaz commented on 2011-11-26 03:44

Hey,

this is what i mean the tabs look different: http://ompldr.org/vYmdodw

It feels weird and sometimes out of place, the spacing and the shadows. I don't rememberever changing any style for firefox so i think this is how it looks by default...

If i there's any way to inprove the look i think many would be happy ;)

Thanks.

flan_suse commented on 2011-11-25 18:33

@Diaz

Do you mean that the tabs in Firefox do not match any theme you apply? (As in they remain the same, regardless of theme?) Or do you mean that the tabs change according to the theme selected, but they still do not look "quite right"? If it's the latter, then I know what you mean. I think that is just how Firefox's XUL interface works. Not sure if there is anything that can be done about it.

Hopefully someone else might have an idea or tweak that can be done for those that are not happy with how Firefox's tabs look.

When using Opera, the tabs look fine to me (closer to how a normal GTK tab would look.) Not perfect, but better.

Diaz commented on 2011-11-24 21:46

Anyone knows if there is any tweaks to do for firefox? I hate how the tabs look in firefox, completly different.

Thanks :)

Anonymous comment on 2011-10-19 18:34

I'm pretty sure somewhere on their site they said that GTK3 support was probably planned for both (in the comments of http://shimmerproject.org/project/albatross/)

flan_suse commented on 2011-10-17 14:31

@nxuul
Thank the awesome folks at ShimmerProject.org. The only Xfce themes I ever use anymore are Albatross, Bluebird, and Greybird: all created by the same project. They are sleek, easy on the eyes, and focus on Xfce / Xfwm, unlike other plain "GTK themes that work under Xfce." A new Xfce theme they are working on, which is yet to be released, is called Shearwater (based on Albatross). It's only proposed at the moment, but I'll definitely make a PKGBUILD for it once it is ready if they do make it into its own independent theme.

Glad you like this!

The other two themes (Albatross and Bluebird) do not have GTK3 support; not sure if they will in the future. But Greybird is definitely my favorite.

flan_suse commented on 2011-10-17 14:28

@nxuul
Thank the awesome folks at ShimmerProject.org. The only Xfce themes I ever use anymore are Albatross, Bluebird, and Greybird: all created by the same project. They are sleek, easy on the eyes, and focus on Xfce / Xfwm, unlike other plain "GTK themes that work under Xfce." A new Xfce theme they are working on, which is yet to be released, is called Shearwater (based on Albatross). I'll definitely make a PKGBUILD for it once it is ready!

Glad you like this!

The other two themes (Albatross and Bluebird) do not have GTK3 support; not sure if they will in the future. But Greybird is definitely my favorite.

Anonymous comment on 2011-10-17 13:38

Just wanted to say great work! I've been waiting on a nice XFCE theme with GTK3 support.

flan_suse commented on 2011-10-03 16:57

Greybird 0.3 was just released with a finished GTK3 theme and various bugfixes.

NOTE: For the GTK3 to work properly (on GTK3 applications such as Evince, NetworkManager, and Eye-of-GNOME), you need to install the unico GTK3 engine. This is currently available on the AUR in the package gtk-engine-unico. This engine was created thanks to Andrea Cimitan, a Canonical developer.

I added gtk-engine-unico as an optdepends, since it is not required for Greybird to work under Xfce.

flan_suse commented on 2011-10-03 16:56

Greybird 0.3 was just released with a finished GTK3 theme and various bugfixes.

NOTE: For the GTK3 to work properly (on GTK3 applications such as Evince, NetworkManager, and Eye-of-GNOME), you need to install the unico GTK3 engine. This is currently available on the AUR in the package gtk-engine-unico.

I added gtk-engine-unico as an optdepends, since it is not required for Greybird to work under Xfce.

flan_suse commented on 2011-08-27 01:55

Greybird 0.2.2 was just released with GTK3 improvements, among other fixes.

flan_suse commented on 2011-06-16 16:18

The Greybird wallpaper is now included.

The wallpaper installs to /usr/share/backgrounds/ (DE-independent), and a symlink is created under /usr/share/xfce4/backdrops/

The wallpaper will automatically load in the list of backgrounds under Settings > Desktop when using Xfce.

For a history of how this great wallpaper came to be, read this short story with images: http://open.knome.fi/2011/03/18/xubuntu-natty-default-wallpaper/

flan_suse commented on 2011-06-10 03:44

A minor update.

I have changed the Shimmer Project PKGBUILDs to use git, instead of the tarballs. This means that the packages are built against distinct "git-tag releases".

Sadly, this requires "git" as a makedep. I hope it's not too big of a deal.

The PKGBUILDs are now cleaner and will not give 404 errors to "dead links".

flan_suse commented on 2011-06-10 02:01

Just got done talking with the Shimmer Project.

Greybird, and the other Shimmer Project Xfce themes, are now using git-tags, which means no more "release" tarballs. Instead, when a state in the git repository is considered "release quality", it will be tagged with a version number. In this case, the PKGBUILD is based on git-tag 0.2.1. This includes the gtk-3.0 theme as well as other modifications to the theme.

I won't use git for this PKGBUILD, since the git-tag can be downloaded in .tar.gz format. This means git isn't needed as a makedep. Less to download, less to worry about.

I am thinking about also including the Greybird wallpaper in the near future, if possible.

flan_suse commented on 2011-06-08 13:05

@jere2001

Just finished talking to the Shimmer Project. They follow the Ubuntu cycle, so any "final release" of a theme will arrive every six months; nothing in between. They might also clean up their repos as well. The next Greybird release will also include the wallpaper with the suite, just like Albatross and Bluebird already do.

In the meantime, someone had made a PKGBUILD for xfce-theme-greybird-git, if you want to try it out. I don't make git PKGBUILDs, because they aren't considered "finished products" since they are constantly being modified and patched up. If you install a PKGBUILD from a git repo one day, and someone else installs the same thing a week later, even though it's the same "version" you both will have two different products. That's another reason I avoid git PKGBUILDs.

We'll see what happens. I might contact them again in the future if there's an issue, but so far it seems we'll have to stick with the current releases of all the Shimmer Project themes, or use the git versions.

Thoughts on this?

flan_suse commented on 2011-06-08 12:58

@jere2001

Just finished talking to the Shimmer Project. They follow the Ubuntu cycle, so any "final release" of a theme will arrive every six months; nothing in between. They might also clean up their repos as well. The next Greybird release will also include the wallpaper with the suite, just like Albatross and Bluebird already does.

In the meantime, someone had made a PKGBUILD for xfce-theme-greybird-git, if you want to try it out. I don't make git PKGBUILDs, because they aren't considered "finished products" since they are constantly being modified and patched up. If you install a PKGBUILD from a git repo one day, and someone else installs the same thing a week later, even though it's the same "version" you both will have two different products. That's another reason I avoid git PKGBUILDs.

We'll see what happens. I might contact them again in the future if there's an issue, but so far it seems we'll have to stick with the current releases of all the Shimmer Project themes, or use the git versions.

Thoughts on this?

flan_suse commented on 2011-06-08 12:58

@jere2001

Just finished talking to the Shimmer Project. They follow the Ubuntu cycle, so any "final release" of a theme will arrive every six months; nothing in between. They might also clean up their repos as well. The next Greybird release will also include the wallpaper with the suite, just like Albatross and Bluebird already does.

In the meantime, someone had made a PKGBUILD for xfce-theme-greybird-git, if you want to try it out. I don't make git PKGBUILDs, because they aren't considered "finished products" since they are constantly being modified and patched up. If you install a PKGBUILD from a git repo one day, and someone else installs the same thing a week later, even though it's the same "version" you both will have two different products. That's another reason I avoid git PKGBUILDs.

We'll see what happens. I might contact them again in the future if there's an issue, but so far it seems we'll have to stick with the current releases of all the Shimmer Project themes, or use the git versions.

Thoughts on this?

flan_suse commented on 2011-06-08 12:58

@jere2001

Just finished talking to the Shimmer Project. They follow the Ubuntu cycle, so any "final release" of a theme will arrive every six months; nothing in between. They might also clean up their repos as well. The next Greybird release will also include the wallpaper with the suite, just like Albatross and Bluebird already does.

In the meantime, someone had made a PKGBUILD for xfce-theme-greybird-git, if you want to try it out. I don't make git PKGBUILDs, because they aren't considered "finished products" since they are constantly being modified and patched up. If you install a PKGBUILD from a git repo one day, and someone else installs the same thing a week later, even though it's the same "version" you both will have two different products. That's another reason I avoid git PKGBUILDs.

We'll see what happens. I might contact them again in the future if there's an issue, but so far it seems we'll have to stick with the current releases of all the Shimmer Project themes, or use the git versions.

Thoughts on this?

flan_suse commented on 2011-06-08 11:12

@jere2001

I'm following the distinct releases by the Shimmer Project, not the changes in the git repo. They haven't released a "stable" Greybird since 0.2 yet, which is odd. I'll contact them to see if they can release a 0.3 or 1.0, like they have been doing with Albatross, Bluebird, and Greybird in the past. For some reason, they don't even include the new Greybird wallpaper yet.

Anonymous comment on 2011-06-07 20:59

New version of Greybird, include GTK3 theme:

https://github.com/shimmerproject/Greybird

flan_suse commented on 2011-02-22 14:33

A quick heads up: Greybird is still incomplete, but is currently being worked on.

flan_suse commented on 2011-02-21 15:45

Shimmer Project has switched from mercurial to Git. PKGBUILD updated accordingly.

flan_suse commented on 2011-02-04 18:13

Package now recommends elementary-icons as an optdepends. This icon set is used by the project to match their Xfce themes.

flan_suse commented on 2011-02-02 18:19

A low saturation Xfce theme complete with an xfwm4 theme. Currently, up to version 0.2, there is no wallpaper.

This theme was created by the Shimmer Project for Xubuntu 11.04.

You can follow them at the Shimmer Project web site, which includes a handful of different art projects: http://www.shimmerproject.org/

flan_suse commented on 2011-02-02 17:43

A low saturation Xfce theme complete with an xfwm4 theme. Currently, up to version 0.2, there is no wallpaper.

This theme was created by the Shimmer Project for Xubuntu11.04.

You can follow them at the Shimmer Project web site, which includes a handful of different art projects: http://www.shimmerproject.org/

flan_suse commented on 2011-02-02 15:43

A low saturation Xfce theme, complete with an xfwm4 theme. Similar in feel to Linux Mint 10's Mint-X theme. Currently, no wallpaper up to version 0.2.

This theme was created by the Shimmer Project, based on the Bluebird Xfce theme.

You can follow them at the Shimmer Project web site, which includes a handful of different art projects: http://www.shimmerproject.org/