> I vote an emphatic No - this would be overhead within proto-core, which
> should remain as _baseline_ as possible (that's my rant and I'm sticking to
> it - proto is a baseline - don't bloat it... please!).
I see that point - and that was the type of discussion that I wanted
to spawn. I agree that the core should not be bloated at all...but
exactly *what* should be in core or not?
> var oldInsert = Element.insert;
> Element.insert = function(...) {... fireYourCustomEvent() ...
> oldInsert(...)};
This is actually a pretty easy way to do that. I don't have a problem
at all implementing this sort of thing outside of the prototype core.
I was just originally thinking that it would help to move Prototype
more towards its goal of creating a level-playing field of sorts - a
core library that irons out all the little cross-browser quirks that
exist (and mutation events are one of those...that was my original
thinking).
Thanks for the comments!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
