All,
I have found a nice animation library that is not as big as
scriptaculous, in my opinion better than moo and that fits pretty good
into the wicket philosophy. I'm talking about animate.js [1].
It is not the most widely adopted javascript library, but it packs a
helluva functionality in
Martijn Dashorst a écrit :
All,
I have found a nice animation library that is not as big as
scriptaculous, in my opinion better than moo and that fits pretty good
into the wicket philosophy. I'm talking about animate.js [1].
It is not the most widely adopted javascript library, but it packs a
I only know scriptaculous and jquery+interface and haven't looked at moo.
But 24Kb for animate is quite interesting!
Frank
On 4/13/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
All,
I have found a nice animation library that is not as big as
scriptaculous, in my opinion better than moo and
On 4/13/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
The animate.js should work out of the box without conflicts with dojo
and prototype. It doesn't redefine core classes, making it orthogonal.
The library is BSD licensed, and seems pretty much 'done'. The 24kb
will be even smaller after
On 4/13/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
And I also remember reading Nathan's blog with a reference to it... :)
A google didn't give results for animate.js, however, he recently
created his own scrolling effect [1]. I don't think his effort is
comparable to animate.js, though fun
On 4/13/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
I'm mainly thinking nice but do you have any concrete plans
(components, behavior) for it?
I think just a behavior (or class) with some examples. The philosophy
of the library is to not create 200 classes for every effect known to
man, which
Martijn Dashorst wrote:
On 4/13/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
I'm mainly thinking nice but do you have any concrete plans
(components, behavior) for it?
I think just a behavior (or class) with some examples. The philosophy
of the library is to not create 200 classes for every
Al Maw a écrit :
Martijn Dashorst wrote:
On 4/13/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
I'm mainly thinking nice but do you have any concrete plans
(components, behavior) for it?
I think just a behavior (or class) with some examples. The philosophy
of the library is to not create 200
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())
I'm sure we can. But the API won't be as straightforward. Bascially
everything you need for an animation is a chunk of javascript, so
prepend/appendJavascript can do the work. But you need some helper
classes to generate the javascript. However, is is more decoupled and
more difficult/uglier to
!) for coding things yourself, the better.
Nathan
--
View this message in context:
http://www.nabble.com/-proposal--adopt-animate.js-into-wicket-extensions-as-our-core-effects-library-tf3570196.html#a9979955
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Martijn Dashorst a écrit :
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){
IJavascriptAnimation { CharSequence getJavascript(); }
AjaxRequestTarget.append(IJavascriptAnimation ani);
AjaxRequestTarget.prepend(IJavascriptAnimation ani);
something like that? that is pretty pluggable.
generalize it even more?
IJavascriptAnimation-IJavascriptProvider
the assumption is
13 matches
Mail list logo
