Re: [proposal] adopt animate.js into wicket-extensions as our core effects library

[Martijn Dashorst]

On 4/13/07, Vincent Demay <[EMAIL PROTECTED]> wrote:

What about a simple Behavior, I think behavior is easier to use for the
end user

class onRefreshAnimationBehavior extends AbstractBehavior{

   onRendered(){
       if(AjaxRequestTarget){
           target.prependJavascript(getFromEffect())
           target.appendJavascript(getToEffect());
       }
    }

    CharSequence getFromEffect();

    CharSequance getToEffect();

}

so user can extend it, ie

onRefreshAnimatedClassBehavior(fromClass, toClass)
in order to do
component.add(new onRefreshAnimatedClassBehavior("yellow", "default"));

This is creating a complete slew of new behaviors. I don't like that.
We have to implement it in a way, that we don't increase the API too
much.

What Al coined seems like a nice option (needs a bit polish imo, but
the basic idea seems sound), *if* we want to support animation as a
core functionality. This would increase the API for the
AjaxRequestTarget. Couldn't we implement it in a less intrusive way,
so that the scriptaculous/dojo/moo fans can plug into our animation
aware target?

Martijn

--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org