I downloaded your library and tried the example sketch. It took me a while to get my head round what was happening because of the lack of documentation but I got there in the end.

So the basic idea is that an animator changes a value from astart value to an end value over the given duration of time (milliseconds I think)  The different animators use diferent equations for the value versus time curve. The value returned by the animator can be used in any way the user wants. Am I right?

In your blog you state:

I plan implement chaining of animators, callback-handlers, repeat suppor, many more animation types and - ahem - more detailed documentation

Please start with the documentation - I know it is a pain in the neck but if you expect people to use your library then user documentation and documented examples are essential.

Some ideas and suggestions.

1. Add another start method that has a single parameter to represent a delayed start e.g. ar.start(1200) - start the animation in 1200 milliseconds time.
2. Chaining of animators is interesting since the 'end value' for the second animator should be the 'start value' for the second animator to avoid discontinuiyties in the animation.
3. You might want to consider whether you want to be able change the animator used before the first animator has finished. In this case the 'start value' for the new animator should be the 'current value'
4. For a truely flexible animation system you might consider simulating your own 'animation event queue' where you create 'events' to triger animation starts, ends, changes etc. So starting an animator would be an event, then when the end value is reached it generates another event which can be used create other start events etc.

The possibbilities are endless but you have made a good start

A final comment - I would have been interested in seeing the source code.

First of all, thanx for trying it and thanx for the feedback

So the basic idea is that an animator changes a value from astart value to an end value over the given duration of time (milliseconds I think)  The different animators use diferent equations for the value versus time curve. The value returned by the animator can be used in any way the user wants. Am I right?

Absolutly right


I've set up a project page for the library in my blog
http://www.local-guru.net/blog/pages/animator

Including some documentation and examples

I really like the idea of adding a delay to the start-function

I also added a download link to the zip-file containig the souce code (which I totally forgot to link in the original blog-post)

Great to see additional library development.  So what do you plan that makes this library different from some of our other animation libraries and why a separate library rather than working on one of the others?     As users look to use an animation library, I think it's important to understand the goals and differences.

Hi,
I think its a bit too early for a feature-comparison yet. I plan to add support for animating PVector objects
to simplify the animation of 2D/3D objects  and the addition of a string parser that allows the definition of a
animation sequence.

I also think that the existence of a great framework shouldn't stop anybody from trying to develop a better one :-)