| 2014-05-01 23:57:59 |
Danielle Foré |
description |
Like the spinner in gtk, we should probably be theming the poofwindow 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. |
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. |
|
| 2014-05-01 23:59:02 |
Danielle Foré |
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. |
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/spinner-01.svg"); }
14% { background-image: url("assets/spinner-02.svg"); }
28% { background-image: url("assets/spinner-03.svg"); }
42% { background-image: url("assets/spinner-04.svg"); }
56% { background-image: url("assets/spinner-05.svg"); }
70% { background-image: url("assets/spinner-06.svg"); }
84% { background-image: url("assets/spinner-07.svg"); }
100% { background-image: url("assets/spinner-08.svg"); }
}
.spinner {
background-color: transparent;
background-image: url("assets/spinner-01.svg");
background-repeat: no-repeat;
background-position: center;
}
.spinner:active {
background-image: url("assets/spinner-01.svg");
animation: spinner 600ms infinite linear;
} |
|
