theme PoofWindow with CSS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Files |
Won't Fix
|
Low
|
Unassigned | ||
Plank |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Like the spinner in gtk, we should probably be theming the poofwindow (the neato poofy cloud animation when you DnD something into the void) from CSS so that the theme/gtk controls the animation speed, amount of frames, etc. I imagine that should reduce a lot of code complexity there.
For reference, the spinner theme CSS looks like this:
@keyframes spinner {
0% { background-image: url("assets/
14% { background-image: url("assets/
28% { background-image: url("assets/
42% { background-image: url("assets/
56% { background-image: url("assets/
70% { background-image: url("assets/
84% { background-image: url("assets/
100% { background-image: url("assets/
}
.spinner {
background-
background-
background-
background-
}
.spinner:active {
background-
animation: spinner 600ms infinite linear;
}
description: | updated |
description: | updated |
Changed in plank: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in pantheon-files: | |
status: | New → Confirmed |
importance: | Undecided → Low |
no longer affects: | egtk |
I think that now that this is getting a code review it might be a good time to speak up. For me the fact that the "poof" effect apes an outdated and inherited idiom from a certain fruity desktop is reason enough to nuke it from space. The cartoony effect looks out of place in a desktop focused on clean design and elegance. Now that pantheon's notifications have a set of modern and appealing animations the inconsistency has become even more dramatic. I believe that the notification appearance animation (reversed and tweaked) provides a template for a more appealing effect.