[Compcomm] Animation depricating Minimize. There is one last thing that minimize can do

[Erkin Bahceci]

On 5/10/07, Sam Spilsbury <smspillaz at gmail.com> wrote:
> On 5/10/07, Erkin Bahceci <erkinbah at gmail.com> wrote:
> > For animation and wobbly, you'll see in the code that both plugins
> > create vertices which are stored in CompWindow structure, and
> > therefore shared, and which the plugins set absolute positions for.
> > What I'm proposing is to make them "add" their "position changes" onto
> > the current positions of those vertices instead of setting absolute
> > positions for them. They just need to know what point on the window
> > each vertex corresponds to (it's a simple list of vertices). This can
> > be done by putting 2 more values (x, y) for each vertex in CompWindow,
> > so that every plugin can compute their "position changes" according to
> > where each vertex corresponds to on the window. Currently each plugin
> > only has this information for the vertices created by itself.
> >
> > For plugins to request creation of vertices in a particular way, there
> > could be core functions like requestRectangularGridVertices and
> > requestRadialGridVertices (this one would be much better for, say, a
> > whirlpool animation), etc. with some resolution. The resolution could
> > be a core option.
> >
> > No need to submit gridmaps or anything else.
>
>
> So you mean like a gripmap interface within compiz? That apps can plug in to?

I don't know what you mean by a "gripmap interface". Combining
animation effects could be done as I tried to describe before. The
vertices are already in the core. Animation and Wobbly plugins create
vertices according to their internal representation of the animation
effect they want to achieve (you could call that a grid). That doesn't
need to be shared.