On Feb 8, 2008 9:19 PM, Nicolás Sanguinetti <[EMAIL PROTECTED]> wrote:
> I'd normally respond that since adding this feature is only 5 lines
> away,
On Feb 9, 2008 6:30 AM, kangax <[EMAIL PROTECTED]> wrote:
> The implementation is NOT as simple as it seems to be.
Teehee :) Ok, point taken. And yup, if it's something "big" it should
come up as a plugin *for now*, but my reasoning on why it should be in
core --encourage people to use this technique-- still stands. What do
the rest think?
Moving on, I'd like to argue on the api ^_^
> Event.register(selector, eventName, handler);
I assume that would catch events at the document level always. I kinda
liked Pat's idea of explicitly passing the element so you could scope
down the events--eg, only handle the events inside that table. Maybe
it's more trouble than it's worth, particularly with keyboard events,
and the performance gain is trivial enough, but I'm guessing that on
fairly complex DOMs it might not be that trivial. What do you think?
> Object.extend(document, {
> delegate: Event.delegate,
> delegators: Event.delegators
> })
Boo. Two different methods to do this? I'd rather let the delegate
method take variable arguments and decide over that, as many functions
in Proto do.
-Nicolas
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
