Quartz Composer effects on notification icons

[GoogleCodeExporter]

Having seen an animation applied to the icon of origin for its notification by 
the likes of "Black Glass" from Ryan Collins (http://www.ryancollins.me/?p=92), 
in which the icon would perform a clockwise turn from 180° starting position 
to a 270° (i.e. the right way up) I thought to myself that more than a simple 
transition could be applied here.

For example inside OS X it comes with Quartz Composer 
(http://en.wikipedia.org/wiki/Quartz_Composer) effects built in, which graphic 
applications like Pixelmator (http://www.pixelmator.com/) take advantage of. 
What set my mind off was the following unnamed draft effort from Rasmus Nielsen 
over at Dribbble http://dribbble.com/shots/288575-Growl in which the icon is 
clearly pixelated.

Now, the follow examples are using the aforementioned Quartz effect, however 
there is no gradient to it, I believe this to be the simple implementation of 
it into Pixelmator rather than it's actual ability, still I see the initial 
icon beginning with a pixelated effect:

http://cl.ly/0K1G2x420K353y1W0t30

….to then focus into recognition the actual icon itself:

http://cl.ly/0M072s3N2X071a2h0Q0v

Of course this would be in the hands of the developer, as they create custom 
notification themes, rathe than to provide endless possibilities for the end 
user, however those do already exist to quite a deep extent in the "Display 
Options" tab already under GROWL.

I would see uses of this in the following scenarios:

1. For normal use, a theme provided for the user for use at their insistence.

2. Naturally the disfigurement of an icon is one trying to either be too clever 
or, possibly, to convey something not quite right. It could therefore be used 
in the case of "Stuffit Expander" when the extraction process is abandoned and 
provisions are in place to let the user be aware of this.

The beauty is that you could leverage these powerful filters as they are built 
into OS X and specifically there for developers and user to improve their 
user's experiences. I think this would be an evolutional step and not too much 
of a difficult one to implement, with many obvious benefits.

Original issue reported on code.google.com by lovel...@gmail.com on 27 Nov 2011 at 3:34

[GoogleCodeExporter]

Original comment by ch...@growl.info on 27 Nov 2011 at 3:48

• Added labels: Product-Growl

[GoogleCodeExporter]

Original comment by ch...@growl.info on 8 Feb 2012 at 3:20

• Added labels: Milestone-Later

[GoogleCodeExporter]

Ah, promising.

Original comment by lovel...@gmail.com on 8 Feb 2012 at 8:02

[GoogleCodeExporter]

2.0 is the milestone after 1.4, and after that we review what's in the later 
milestone to cherry pick things for the next version. That's how the later 
milestone works, fyi. :)

Original comment by ch...@growl.info on 8 Feb 2012 at 8:18

[GoogleCodeExporter]

It's all about priorities.

Original comment by lovel...@gmail.com on 8 Feb 2012 at 8:59