As Mitchell says lists of that size aren't going to perform brilliantly anyway, but the plugin only adds markup when an options menu is visible and cleans up again after it is closed so the performance impact shouldn't be too bad unless you are opening options menus on all 500+ list items at once.
Saying this, I've not done any formal performance tests so these comments are theoretical...
If you end up throwing together a test case with large numbers please post up the findings
Want to build better Sencha apps? Check out my free email course Best Practices for Improving your Sencha Apps
Learn Ext JS 6 with my new ebook - Ext JS 6: Getting Started. Get a Sample Chapter now!
Need help with Sencha development, code reviews or training? Get in touch!
Has anybody checked it in Sencha Touch 2.0? I have problem with that. I placed "Ext.ux.touch.ListOptions.js" in my site directory, copied css files also, added info about all this stuff in my index.html and added plugin in my list and now I see an error message in Ext.ux.touch.ListOptions.js:
And another one related with previous:Code:Ext is not defined
It seems that it can't find Ext.ux.touch with this code in Ext.ux.touch.ListOptions.js:Code:Cannot read property 'touch' of undefined
How to solve it?Code:Ext.ns('Ext.ux.touch');
I solved my problem. Now I have some success in porting of this component to Sencha Touch 2.0 but there are some problems. All interested persons are invited in discussion: http://www.sencha.com/forum/showthre...856#post772856