Suppose I want to make an alt-backtick window switcher that is themable, and that cycles through windows. I am imagining that I could set
classes on the actor/element depending on state:
previous is for windows before the currently-selected window, and
next is for windows after the currently selected window. Then I could also supply configurable
animateToPosition parameters, or something. Then people could theme that, and they could add 3D rotation like in the Coverflow extension using CSS.
That may be a good use for
Maybe you’re imagining that we wouldn’t want to apply
matrix3d to, say, the title bar. That’s probably true for the most part, but we can’t imagine everything people want to make, we can only give them the tools to make anything.
Now I’m imagining the KNotifier extension with icons that rotate around Y (assuming Y is up/down on the screen and that the CSS has the same coordinate system as in HTML’s CSS) that are triggered by simply adding/removing a class that is associated with a CSS animation, and the developer not having to imperatively manage all that animation stuff and making bugs.
I suppose CSS
transform maps to a ClutterActor’s
transform, and I don’t see why
matrix3d would be a bad idea if it allows some neat tricks.