Re: [Proto-Scripty] Re: Class Inheritance & Properties

Ah okay, so you can use "Parent.prototype.method.call()" as an alternative for the $super argument? Would that be better to use for performance critical apps instead of the $super argument? On Mon, Nov 29, 2010 at 8:03 PM, T.J. Crowder wrote: > Hi, > > From within a call to `SectionText`'s `exte

Re: [Proto-Scripty] Event capture

http://api.prototypejs.org/dom/Event/observe/ Changes in 1.6.x Prior to Prototype 1.6, Event.observe supported a fourth argument (useCapture), a boolean that indicated whether to use the browser's captu

[Proto-Scripty] Re: Class Inheritance & Properties

Hi, > Ah okay, so you can use "Parent.prototype.method.call()" as an alternative > for the $super argument? Yes. The first argument to `call` is the value to use as `this` during the call (so if you're calling it from within a subclass, you'd supply `this`). Subsequent arguments, if any, are pass

Re: [Proto-Scripty] Event capture

On Tue, Nov 30, 2010 at 3:11 AM, Johan Arensman wrote: > http://api.prototypejs.org/dom/Event/observe/ > > Changes in 1.6.x > > Prior to Prototype 1.6, Event.observe supported a fourth argument > (useCapture), a boolean that indicated whether to use the browser's > capturing phase or its bubbling

[Proto-Scripty] compatible versions 1.5

Hi my name is Robin and I am developing for a quit big site which is running prototype 1.5. We looking into upgrading to 1.6 or 1.7. I´m wondering if it´s safe to upgrade to 1.6 or 1.7 and ecspect everythin to workwhat should I watch out for? Also, what versions of scriptaculous is compatibl

[Proto-Scripty] Re: compatible versions 1.5

Hi, I never used 1.5, but my impression is that a lot changed between 1.5 and 1.6. Your best bet is to look through the change log[1], it's been more than three years since 1.6 and people will have forgotten a lot. Unfortunately, just searching for "incompatible" in the change log will miss thing