[Compcomm] Animation plugin

[Mike Dransfield]

Erkin Bahceci wrote:
> Hi,
>
> For the widget thing, you mean you want the secondary windows to have
> a different animation effect than widgets (and primary windows),
> right? (Otherwise you could use | to match them too of course).
>   

What I am really looking for is an arbitrary number of effects
on multiple windows.  ie.

normal window create / close = zoom
tooltip/dialog/menu create / close = fade
email client window, which has title 'Compose:' close = airplane flies away
widget create / close = beam up + burn

etc etc (new plugins may add other match handlers for extra types)

this is not possible with only create 1/2 and close 1/2

> And I didn't see a CompOptionGroup discussion. Where is it? I could
> have a look at that.
>   

It was fairly small and went something like this

David : I was thinking of adding CompOptionGroup
Me : That sounds useful
David : Lets wait til 0.5.0 and ini plugin done etc and we have a better
idea of the requirements.
Me : Cool

> What I had in mind was an option exception list consisting of strings
> in the format
>   "<Window Match>:<Event>:<Option>:<Value>"
> such as
>   "type=Normal | Dialog:close:effect:Burn",
>   "type=Normal | Dialog:any:fire_direction:Up",
>   "any:minimize:glide1_away_angle:45",
>   etc...
>   

CompOptionGroup would prevent you having to use the extra
delimiters and I assume it would make it easier to read internally.
Otherwise it is the same idea.

Look at the code for the opacity_match in core because this is
the same thing but with 2 lists rather than 1 list with delimiters.

My mousegestures plugin does the same thing with : separated
strings (its not nice to work with for anyone).

> These exceptions would be prioritized over the normal options. There
> could optionally be a nice settings-manager gui frontend for this
> exception string list, if the necessary selection choices, etc. are
> specified somewhere generically and automatically (at least for
> <Option>). <Event> selection list would be pretty much fixed (Any,
> Create, Close, Minimize, Unminimize, Shade, Unshade for now).
>   

Using the existing CompOption types would (I think) mean
that you would not have to do this sort of thing.

The GUI could handle it as a columned list, with each GUI handling
it their own way.

> Cheers,
> Erkin
>
> On 5/2/07, Mike Dransfield <mike at blueroot.co.uk> wrote:
>   
>> Did you ever see the initial discussion of a CompOptionGroup type?
>>
>> It will be some way of grouping lists, I think the animation plugin
>> can use it to create any number of animation schemas.  The group
>> could be like this:
>>
>> match, effect, duration
>>
>> There would be 1 group for each type of animation (minimize, close,
>> shade etc) and each item is a list.
>>
>> I have just been testing the new animation matches along with the
>> pywidget plugin, I set the create and close to this.
>>
>> close1_match=(type=Normal | Dialog | ModalDialog | Utility) &
>> override_redirect=0 & widget=0
>> close2_match=widget=1
>> create1_match=(type=Normal | Dialog | ModalDialog | Utility) &
>> override_redirect=0 & widget=0
>> create2_match=widget=1
>> close2_effect=Burn
>> create2_effect=Magic Lamp 3 (Vacuum)
>>
>> It means that screenlets look really cool but I have lost animations
>> on my secondary windows.
>>
>>
>>     
>>> Which separate effects do you use btw?
>>>
>>> Regards,
>>> Erkin
>>>
>>> On 5/2/07, Sam Spilsbury <smspillaz at gmail.com> wrote:
>>>
>>>       
>>>> what, NO! I use a different effect for minize/unminimize!
>>>>
>>>>
>>>> On 5/2/07, Erkin Bahceci <erkinbah at gmail.com> wrote:
>>>>
>>>>         
>>>>> Hi,
>>>>>
>>>>> Minimize/unminimize, and shade/unshade pairs are merged now.
>>>>>
>>>>> - Erkin
>>>>>
>>>>> On 4/23/07, Bellegarde Cedric <gnumdk at gmail.com> wrote:
>>>>>
>>>>>           
>>>>>> I do some works on animation plugin and have some question about it...
>>>>>>
>>>>>> Do we really need a different effect on minimize/unminimize,
>>>>>>
>>>>>>             
>>>> shade/unshade?
>>>>
>>>>         
>>>>>> I can add create1/close1, create2/close2 event if i think having a
>>>>>>
>>>>>>             
>>>> different
>>>>
>>>>         
>>>>>> effect can be justified here...
>>>>>>
>>>>>> Cedric
>>>>>>
>>>>>> _______________________________________________
>>>>>> CompComm mailing list
>>>>>> CompComm at Rock3d.org
>>>>>> http://www.ubaight.com/mailman/listinfo/compcomm
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>>>> _______________________________________________
>>>>> CompComm mailing list
>>>>> CompComm at Rock3d.org
>>>>> http://www.ubaight.com/mailman/listinfo/compcomm
>>>>>
>>>>>
>>>>>           
>>>> _______________________________________________
>>>> CompComm mailing list
>>>> CompComm at Rock3d.org
>>>> http://www.ubaight.com/mailman/listinfo/compcomm
>>>>
>>>>
>>>>
>>>>         
>>> _______________________________________________
>>> CompComm mailing list
>>> CompComm at Rock3d.org
>>> http://www.ubaight.com/mailman/listinfo/compcomm
>>>
>>>       
>> _______________________________________________
>> CompComm mailing list
>> CompComm at Rock3d.org
>> http://www.ubaight.com/mailman/listinfo/compcomm
>>
>>     
> _______________________________________________
> CompComm mailing list
> CompComm at Rock3d.org
> http://www.ubaight.com/mailman/listinfo/compcomm
>