I'd say your DOM traversals might add quite a bit of weight to your filter. Why select the LI element if you're really looking at its child A element's innerHTML property ? Select those nodes and skip the execution of down, should speed things up quite a bit.
Also if you're using a text input control then why not use keydown or keyup events to trigger the filter instead of a timer? Timers (Intervals) add weight to the app, also it could execute as the user is typing which could slow down data entry before the user has finished what they were hoping to filter by. If you do go for a key event put a timeout on it such that it won't execute until the user has *finished* typing, if you filter on each keystroke and the user types fast it could really gum things up. On Dec 1, 1:52 pm, Walter Lee Davis <[EMAIL PROTECTED]> wrote: > Wow, thanks! Had no idea. > > Walter > > On Dec 1, 2008, at 1:46 PM, Diodeus wrote: > > > > > "Performant" isn't a word. > > >http://weblogs.asp.net/jgalloway/archive/2007/05/10/performant-isn-t-... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" 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-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
