Roassal animations

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Roassal animations

Uko2
Hi,

what do you thing about replacing ROPluggableAnimation's>>doStep

`block value`

with

`block cull: self elapsedCycles`?

Because this way you can have a block hooked to the number of cycle.

Cheers.
Uko
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal animations

abergel
Yes and no :-)

I think the animation component in Roassal should be redone. It is currently based on the amount of refresh occurring in the view. It should instead be based on the time passing.
Instead of saying you want to move an element during 10 cycles, you should stay 500 milliseconds.

Igor showed me Viva at esug. It contains some good ideas.

I will work on it right now...

Alexandre



On Oct 16, 2013, at 8:39 AM, Yuriy Tymchuk <[hidden email]> wrote:

> Hi,
>
> what do you thing about replacing ROPluggableAnimation's>>doStep
>
> `block value`
>
> with
>
> `block cull: self elapsedCycles`?
>
> Because this way you can have a block hooked to the number of cycle.
>
> Cheers.
> Uko
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal animations

abergel
In reply to this post by Uko2
Hi Uko,

I've just committed a new version of Roassal that contains a class ROTimelyAnimation. On some point, all the animations should be a subclass of that class.
I have also produced ROLinearMoveT and ROPluggableAnimationT as you seems to need it. You are very welcome to contribute to it to fit your need.

Some usage:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| view el |
view := ROView new.
el := (ROBox blue size: 30) element.
view add: el.
ROLinearMoveT new for: el to: 200 @ 60 during: 500.
view open.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| view el |
view := ROView new.
el := (ROBox blue size: 30) element.
view add: el.
ROPluggableAnimationT new
        block: [ :animation | el translateTo: (animation elapsedTimeNormalized * 500) @ 0 ];
        duration: 2000;
        on: view.
view open.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

As you can see, you provide a duration in milliseconds. I have also used #cull: as you suggested. This is indeed a good point.

The important point of these animations, is that are based on the elapsed time. #elapsedTimeNormalized returns a value between 0.0 and 1.0. If 1.0, the animation has ended. I took these ideas form Igor's Viva.

Cheers,
Alexandre


On Oct 16, 2013, at 8:39 AM, Yuriy Tymchuk <[hidden email]> wrote:

> Hi,
>
> what do you thing about replacing ROPluggableAnimation's>>doStep
>
> `block value`
>
> with
>
> `block cull: self elapsedCycles`?
>
> Because this way you can have a block hooked to the number of cycle.
>
> Cheers.
> Uko
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal animations

Uko2
Thank you.

I'll give it a try.

On Oct 16, 2013, at 5:16 PM, Alexandre Bergel <[hidden email]> wrote:

> Hi Uko,
>
> I've just committed a new version of Roassal that contains a class ROTimelyAnimation. On some point, all the animations should be a subclass of that class.
> I have also produced ROLinearMoveT and ROPluggableAnimationT as you seems to need it. You are very welcome to contribute to it to fit your need.
>
> Some usage:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> | view el |
> view := ROView new.
> el := (ROBox blue size: 30) element.
> view add: el.
> ROLinearMoveT new for: el to: 200 @ 60 during: 500.
> view open.
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> | view el |
> view := ROView new.
> el := (ROBox blue size: 30) element.
> view add: el.
> ROPluggableAnimationT new
> block: [ :animation | el translateTo: (animation elapsedTimeNormalized * 500) @ 0 ];
> duration: 2000;
> on: view.
> view open.
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> As you can see, you provide a duration in milliseconds. I have also used #cull: as you suggested. This is indeed a good point.
>
> The important point of these animations, is that are based on the elapsed time. #elapsedTimeNormalized returns a value between 0.0 and 1.0. If 1.0, the animation has ended. I took these ideas form Igor's Viva.
>
> Cheers,
> Alexandre
>
>
> On Oct 16, 2013, at 8:39 AM, Yuriy Tymchuk <[hidden email]> wrote:
>
>> Hi,
>>
>> what do you thing about replacing ROPluggableAnimation's>>doStep
>>
>> `block value`
>>
>> with
>>
>> `block cull: self elapsedCycles`?
>>
>> Because this way you can have a block hooked to the number of cycle.
>>
>> Cheers.
>> Uko
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal animations

Stéphane Ducasse
In reply to this post by abergel

On Oct 16, 2013, at 2:19 PM, Alexandre Bergel <[hidden email]> wrote:

> Yes and no :-)
>
> I think the animation component in Roassal should be redone. It is currently based on the amount of refresh occurring in the view. It should instead be based on the time passing.
> Instead of saying you want to move an element during 10 cycles, you should stay 500 milliseconds.
>
> Igor showed me Viva at esug. It contains some good ideas.

Please extend viva because it is full of good ideas and pain gor got on previous projects.

Stef


>
> I will work on it right now...
>
> Alexandre
>
>
>
> On Oct 16, 2013, at 8:39 AM, Yuriy Tymchuk <[hidden email]> wrote:
>
>> Hi,
>>
>> what do you thing about replacing ROPluggableAnimation's>>doStep
>>
>> `block value`
>>
>> with
>>
>> `block cull: self elapsedCycles`?
>>
>> Because this way you can have a block hooked to the number of cycle.
>>
>> Cheers.
>> Uko
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal animations

Stéphane Ducasse
In reply to this post by abergel
Alex

did you have a real look at Viva?

Stef

On Oct 16, 2013, at 5:16 PM, Alexandre Bergel <[hidden email]> wrote:

> Hi Uko,
>
> I've just committed a new version of Roassal that contains a class ROTimelyAnimation. On some point, all the animations should be a subclass of that class.
> I have also produced ROLinearMoveT and ROPluggableAnimationT as you seems to need it. You are very welcome to contribute to it to fit your need.
>
> Some usage:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> | view el |
> view := ROView new.
> el := (ROBox blue size: 30) element.
> view add: el.
> ROLinearMoveT new for: el to: 200 @ 60 during: 500.
> view open.
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> | view el |
> view := ROView new.
> el := (ROBox blue size: 30) element.
> view add: el.
> ROPluggableAnimationT new
> block: [ :animation | el translateTo: (animation elapsedTimeNormalized * 500) @ 0 ];
> duration: 2000;
> on: view.
> view open.
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> As you can see, you provide a duration in milliseconds. I have also used #cull: as you suggested. This is indeed a good point.
>
> The important point of these animations, is that are based on the elapsed time. #elapsedTimeNormalized returns a value between 0.0 and 1.0. If 1.0, the animation has ended. I took these ideas form Igor's Viva.
>
> Cheers,
> Alexandre
>
>
> On Oct 16, 2013, at 8:39 AM, Yuriy Tymchuk <[hidden email]> wrote:
>
>> Hi,
>>
>> what do you thing about replacing ROPluggableAnimation's>>doStep
>>
>> `block value`
>>
>> with
>>
>> `block cull: self elapsedCycles`?
>>
>> Because this way you can have a block hooked to the number of cycle.
>>
>> Cheers.
>> Uko
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal animations

Tudor Girba-2
In reply to this post by Stéphane Ducasse
Hi,

What is Viva?

Doru


On Thu, Oct 17, 2013 at 8:02 AM, Stéphane Ducasse <[hidden email]> wrote:

On Oct 16, 2013, at 2:19 PM, Alexandre Bergel <[hidden email]> wrote:

> Yes and no :-)
>
> I think the animation component in Roassal should be redone. It is currently based on the amount of refresh occurring in the view. It should instead be based on the time passing.
> Instead of saying you want to move an element during 10 cycles, you should stay 500 milliseconds.
>
> Igor showed me Viva at esug. It contains some good ideas.

Please extend viva because it is full of good ideas and pain gor got on previous projects.

Stef


>
> I will work on it right now...
>
> Alexandre
>
>
>
> On Oct 16, 2013, at 8:39 AM, Yuriy Tymchuk <[hidden email]> wrote:
>
>> Hi,
>>
>> what do you thing about replacing ROPluggableAnimation's>>doStep
>>
>> `block value`
>>
>> with
>>
>> `block cull: self elapsedCycles`?
>>
>> Because this way you can have a block hooked to the number of cycle.
>>
>> Cheers.
>> Uko
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal animations

abergel
In reply to this post by Stéphane Ducasse
> did you have a real look at Viva?

I cannot find Viva on Smalltalkhub.

Alexandre

>
> On Oct 16, 2013, at 5:16 PM, Alexandre Bergel <[hidden email]> wrote:
>
>> Hi Uko,
>>
>> I've just committed a new version of Roassal that contains a class ROTimelyAnimation. On some point, all the animations should be a subclass of that class.
>> I have also produced ROLinearMoveT and ROPluggableAnimationT as you seems to need it. You are very welcome to contribute to it to fit your need.
>>
>> Some usage:
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> | view el |
>> view := ROView new.
>> el := (ROBox blue size: 30) element.
>> view add: el.
>> ROLinearMoveT new for: el to: 200 @ 60 during: 500.
>> view open.
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> | view el |
>> view := ROView new.
>> el := (ROBox blue size: 30) element.
>> view add: el.
>> ROPluggableAnimationT new
>> block: [ :animation | el translateTo: (animation elapsedTimeNormalized * 500) @ 0 ];
>> duration: 2000;
>> on: view.
>> view open.
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>
>> As you can see, you provide a duration in milliseconds. I have also used #cull: as you suggested. This is indeed a good point.
>>
>> The important point of these animations, is that are based on the elapsed time. #elapsedTimeNormalized returns a value between 0.0 and 1.0. If 1.0, the animation has ended. I took these ideas form Igor's Viva.
>>
>> Cheers,
>> Alexandre
>>
>>
>> On Oct 16, 2013, at 8:39 AM, Yuriy Tymchuk <[hidden email]> wrote:
>>
>>> Hi,
>>>
>>> what do you thing about replacing ROPluggableAnimation's>>doStep
>>>
>>> `block value`
>>>
>>> with
>>>
>>> `block cull: self elapsedCycles`?
>>>
>>> Because this way you can have a block hooked to the number of cycle.
>>>
>>> Cheers.
>>> Uko
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal animations

abergel
In reply to this post by Tudor Girba-2
A small set of classes to do animation in Athens
I cannot find the repo however.

Alexandre


On Oct 17, 2013, at 3:07 AM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> What is Viva?
>
> Doru
>
>
> On Thu, Oct 17, 2013 at 8:02 AM, Stéphane Ducasse <[hidden email]> wrote:
>
> On Oct 16, 2013, at 2:19 PM, Alexandre Bergel <[hidden email]> wrote:
>
> > Yes and no :-)
> >
> > I think the animation component in Roassal should be redone. It is currently based on the amount of refresh occurring in the view. It should instead be based on the time passing.
> > Instead of saying you want to move an element during 10 cycles, you should stay 500 milliseconds.
> >
> > Igor showed me Viva at esug. It contains some good ideas.
>
> Please extend viva because it is full of good ideas and pain gor got on previous projects.
>
> Stef
>
>
> >
> > I will work on it right now...
> >
> > Alexandre
> >
> >
> >
> > On Oct 16, 2013, at 8:39 AM, Yuriy Tymchuk <[hidden email]> wrote:
> >
> >> Hi,
> >>
> >> what do you thing about replacing ROPluggableAnimation's>>doStep
> >>
> >> `block value`
> >>
> >> with
> >>
> >> `block cull: self elapsedCycles`?
> >>
> >> Because this way you can have a block hooked to the number of cycle.
> >>
> >> Cheers.
> >> Uko
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev