Mislav Marohnić wrote:
> ...
>
>     - Expand Prototype custom events to fire callbacks for Element methods
>     such as update, setStyle, remove, replace, insert, wrap,
>     writeAttribute,
>     addClassName, removeClassName, scrollTo, etc.
>
>
> That is planned for the next major release. Based on how it performs, 
> it may be pushed further down the road. We'll see.
Awesome! I've always seen the value for consistently using the "wrapper" 
functions above (i.e. instead of using innerHTML, className, etc.) is 
the prospect of callbacks.

>     - Add support for callback registration and multiple callbacks for SAU
>     Effect events 
>
>
> Is the current model for callbacks in script.aculo.us 
> <http://script.aculo.us> too limiting? It would be better if you would 
> explain this request with an example.
> ...
>
// for example, attach callbacks at any point without having to compose 
a new function
var myeffect = Effect.Grow('mydiv', {afterFinish: mycallback1});
//...
myeffect.observe('afterFinish', mycallback2);


// current approach (is this even correct? it is confusing)
var fn = myeffect.options.afterFinish;
myeffect.options.afterFinish = function() {
fn.apply(this, arguments);
mycallback2.apply(this, arguments)
};



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to