[Compcomm] Animation plugin

[Erkin Bahceci]

On 4/23/07, Mike Dransfield <mike at blueroot.co.uk> wrote:
> Did you ever think of splitting the animation plugin into
> a controller and an animation part?
>
> The controller could use complicated window matching rules
> to determine per window animations.  It could then set X hints
> on each window for each transition effect.
>
> If the animation plugin finds one of these hints then it can use
> that animation, otherwise it would fall back to a default.  If it
> does not provide that animation then it should do nothing.
>
> This way many animation plugins could be run at once without
> clashing if they all respect the animation controllers hints.
>
> The core fade and minimize could also be changed to respect
> them which I think would solve a lot of other problems.
>
> This would keep everyone happy without making the animation
> plugin more complicated.
>

I agree, that would be a good thing to do. Plugins such as Wobbly,
Minimize, effect implementation parts of Animation, (and maybe Fade)
could act as animation providers. And Animation's controller would
simply set X hints on windows as you said.


> >> I can add create1/close1, create2/close2 event if i think having a different
> >> effect can be justified here...
> >>
> >
> > Btw what do you mean by "add"?
> >
>
> I hope you are all aware that the notifications will change
> very soon, it will be an awful lot easier to work out if a window
> is minimizing or unmapping.
>
> David seems to like the solution of making the notification
> functions into wrappable functions.  It should be fairly easy to
> implement these things quickly which would mean less code and
> work for animation.

Yes, that will simplify the Animation plugin.

Regards,
Erkin