I agree that onmouseover is obtrusive, but in this instance, I've
chosen obtrusive code to gain performance. I'm open to a less
obtrusive solution though, especially if it'll save me disk space.
Ivan, I've tested it in FireFox, IE7, and Chrome. Works great on
those.
Tom, that makes a ton of sense about IE's event namespace. I
understand what you're saying about adding event's by using $
('el').addEvent() I've made an assumption that it will perform as bad
as var Tips1 = new Tips($$('.Tips1')); on page load, due the need to
traverse the DOM. I could be wrong though, I haven't tested it. Maybe
I'll try that tonight.
Nutron, thanks for the tips! Putting it in a class makes a ton of
sense. I'll do that to clean things up.
No one mentioned an opinion about detaching the element from Tips on
mouse out. Do you think that's worth the effort or does MooTools have
good garbage collection? I'm planning on running some tests on memory
usage later, just wanted to get a general idea from the group.
Thanks again for the help guys!
Dusty
On Oct 14, 3:52 pm, "Iván N Paz" <[EMAIL PROTECTED]> wrote:
> > By doing in-line onclick assignments, it's probably much, much faster.
>
> But that would make for javascript that would be very obtrusive....
>
> > Event delegation won't work, because you'd have to capture the mouseover
> > event for the parent, which probably contains all 3000 of these but is only
> > fired when the mouse enters the area the first time.
>
> mousemove and check object below (target?) would pose the same
> problem/performance issue??
>
> Well... anyways.... he seems he found the solution though, hey Dusty,
> have you tested it crossbrowser already????
>
> Cheers
> Iván
