I highly suggest just rewriting your event:selectors code to use pure
Prototype. There are major inefficiencies inherent in event:selectors
api that probably could be remedied but aren't:
var Rules = {
'span.someClass a:mouseover': function(){ ... },
'span.someClass a:mouseout': function(){ ... },
'span.someClass a:click': function(){ ... }
};
That is calling $$('span.someClass a') elements once for each selector,
a considerable performance hit on any sizable DOM.
Consider:
$$('span.someClass').each(function(el){
el.observe('mouseover',function(){};
el.observe('mouseout',function(){};
el.observe('click',function(){};
//can also do non-event related things like
new Ajax.InPlaceEditor(el);
}
Or, for single observers
$$('<some selector>','<another
selector>').invoke('observe','click',function(){});
The "reapply all selectors onComplete of an ajax request" is also highly
inefficient. event:selectors was ok, but it is really just another
library to be maintained IMHO. That said, you could probably fix it
yourself easily enough, it is probably an issue with the fact that it
uses ._each instead of .each..
Colin
[EMAIL PROTECTED] wrote:
> Hey, after the release of prototype 1.5, i've noticed issues with
> event:selectors http://encytemedia.com/event-selectors/
>
> It might just be me, but I can't get the "loaded" event to work
> correctly anymore. Also, with prototype 1.5.1_rc1, event:selectors
> doesn't work at all...
>
> Does any body else experience this? Will there be a fix?
>
>
> >
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
