Hi
Viva is a small framework to define animation developed by igor Stasenko. It is used by Roassal2 for its animation. Now Viva is published in its own repository MCHttpRepository location: 'http://www.smalltalkhub.com/mc/RMoD/Viva/main' user: '' password: '' and published in the configuration repository for Pharo 40. Stef |
2015-03-15 21:34 GMT+01:00 stepharo <[hidden email]>: Hi Looks good, pretty much what I had in mind for a basic animation framework. How about making the animated value more generic and independent of a timer, more like a "binding" source -> property binding -> target and an (timer-)animated binding timer as source -> property binding -> target As I was thinking about an animation framework I got the idea of some more generic components. The components I had in mind: Clock EventQueue Task Binding or PropertyWrapper Range (as a source for interpolators) Interpolators Transition/Animation ( connection of a source(timer) and property bind, together with a range interpolator). scaling/easing function (linear/quad/quadIn/quadOut) Clock, EventQueue and Task classes (maybe we have some of them already) may be usable for other things and are used here as building blocks for the (transition/animation) framework. (The idea is, to not invent a TimerFrameWorkClock/ TimerFrameWorkEvent / TimerFrameWorkXXX....) Do you know this Squeak (Morphic) Animation Framework I like how it wraps different property animation in different animation classes (AlphaBlendAnimation/ColorAnimation ...). (I wonder why it is nowhere used) And there is GLMAnimation, but I don't like how it is implemented. nicolai |
> Looks good, pretty much what I had in mind for a basic animation
> framework. Hi nicolai I still do not fully understand it :) I mean I could try to look smart and say yes. But there is a little voice in my head that said that I do not understand the little details. I think that I would have to rebuild or check all the code before. :) so this is why I stay humble :) > How about making the animated value more generic and independent of a > timer, more > like a "binding" > source -> property binding -> target > and an (timer-)animated binding > timer as source -> property binding -> target feel free to enhance it. Igor developed it in 2 days and we coded the turtle as an example so that I understand it but I failed :) > As I was thinking about an animation framework I got the idea of some > more generic > components. The components I had in mind: > Clock > EventQueue > Task > Binding or PropertyWrapper > Range (as a source for interpolators) > Interpolators > Transition/Animation ( connection of a source(timer) and property > bind, together with a range interpolator). > scaling/easing function (linear/quad/quadIn/quadOut) > Clock, EventQueue and Task classes (maybe we have some of them already) > may be usable for other things and are used here as building blocks > for the (transition/animation) framework. > (The idea is, to not invent a TimerFrameWorkClock/ TimerFrameWorkEvent > / TimerFrameWorkXXX....) > could use it. > > Do you know this Squeak (Morphic) Animation Framework > (https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/animations) > ? > I like how it wraps different property animation in different > animation classes (AlphaBlendAnimation/ColorAnimation ...). No I did not know it. I will add it to the list of things that I want to understand. First I should study for real Viva. > (I wonder why it is nowhere used) > > > And there is GLMAnimation, but I don't like how it is implemented. > So several propositions: - improve viva - design your own (check in block because alain has the logic for alarm and ticking) - are you interested to participate to a paper that we want to send to IWST on Viva (but it could be on animation frameworks). > > nicolai > > > > > > > |
Free forum by Nabble | Edit this page |