在几乎两天的搜索和研发之后;D 最后,我得出了我认为值得和适合我的网络应用的、基于“质量”的碎片。
我推出一个基于MVC2的网络应用程序,I m在伙伴关系中开发。 净额C#. I ve L2S(LINQ至QQ)是我的DAL,我利用服务层结构通过L2S收集数据。
Now, I m going to have some "Look ups" in which the list of selection might be big (i.e. 1000 or more records) so at times I want my auto-complete look up to be dynamic (i.e. I give the page from which it ll get the values and show in the dropdown) But there re simple ones also like 10-20 values which I want to render statically.
In short I need something v.simple and straight forward auto-complete plugin which does the job without asking me too many questions or requiring too many .js files (of course excluding jQuery).
随同我的结论,随函附上我的“研发”摘要——
- Simpler, static, has contains search( http://frontensemble.com/hyjack/)
- Simple, static/dynamic, only starts with search(
http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/)
- Complex, static/dynamic, combobox like contains search and much more ( http://jqueryui.com/demos/autocomplete/ http://docs.jquery.com/UI/Autocomplete/ )
- Simpler, static/dynamic, has contains search ( http://www.dyve.net/jquery?autocomplete )
*Pls consider the (dot) above as my ratings. After some insights and demo reviews I ve concluded that I ll go with #4 the dyve.net auto-complete plugin because it seems to be doing everything I need and most importantly its not complex.
你们发现,第3号功能丰富,其规模远远大于其规模,因此我可以选择。 FYI, #2不过是第3号的主要版本(但我面临的唯一问题是,它(第2号)只是开始配对,其中的配对更好)。
希望一线前进。
EDIT:
Well after a night-out and more then 20 hours of struggling and experimenting. I conclude that with jQuery I need to choose something which has a bigger support. With option #4 -The main problem came in when I wanted to populate a child dropdown based on parent It does populate dynamically but it persists the old items as well so while searching - the old ones will popup! I tried its cacheFlush, etc.. but it didn t worked. Finally, I posted my comment on the author s google code page and left it.
- My final take would be to use jQueryui - well I can do with some complexity when I m getting too many other plugins who share the same library. So, my vote goes to option #3