Each browser performs differently, because of how the plugin takes the
original set of DOM nodes (list items, usually) and moves them around in
the DOM. Basically, IE6 sux wind, but IE7+ is OK. Safari and Chrome
seemed to be the fastest in my not-so-scientific tests. Firefox 3+ was OK.
I didn't try it with 1500 items. I think the most I tested was around
400. If you have the 1500 items already getting rendered, it shouldn't
be too hard to plug it in and see what happens. I suspect it might take
a noticeable "while" to load. I've thought about some alternate
approaches for loading large sets of items or making it easy to show a
loading message (at worst), but haven't set down to code any of them yet.
You might want to experiment by capturing the HTML from the plugin demo
page and adding your items to one of the demos.
If your items aren't changing often, there might be a way to dump out
the generated HTML and reuse that as static HTML, but it'd take some
chopping on the plugin to get rid of the stuff that creates the HTML.
If you don't need to use the includeOther:true option, you could prefix
the items you want to exclude with some text other than A-Z and 0-9.
- Jack
Workingman wrote:
Is there a limit to the number of lines that the menu can handle.
Meaning if I give it 1500 or so names of "products" that I would like
it to filter and display under the associated letter or number.
As an "ancillary" question is there a way to "exclude" prefixes that
would mean that they would "never" be considered as a first letter in
the menu?
Thanks in advance for any help/advice.
