Just for those scoring at home, I’ve moved GWTaculous, my effort to rewrite Scriptaculous in GWT, over to GWT 1.4. I’ve also gotten Fade working on IE6. Sorry, nothing to see yet, but hopefully next week I’ll have time to put up a side-by-side demo of GWTaculous and Scriptaculous.
All of that being said, performance is fine in Firefox, Safari, Opera and IE7, but somewhat uneven in IE6. My suspicion is that the iterator I’m using may be too fat for the effects queue loop.
Iterator it = queue.iterator(); long now = System.currentTimeMillis(); while (it.hasNext()) { EffectHooks effect = (EffectHooks) it.next(); if (effect.isDone()) { it.remove(); } else { effect.loop(now); } } // since we may have removed some effects, we should check to see if our queue is empty if (queue.size() == 0) { stopTimer(); }
I’ll do a little bit of profiling, but since IE6 is on it’s way out, I’m wondering if I should really worry about it. Premature optimization is the root of all evil.
Technorati Tags: ajax, gwt, scriptaculous, gwtaculous
