3 Nov 2011 3:16 PM #1
Unanswered: Download ItemSelector.js and MultiSelect.js
I am new bie to ExtJS 4. I am trying to use MultiSelect and ItemSelector components in my application.
These are not available in standard ExtJS distribution. Can you please let me know where can I download these components. These are under 'ux' package.
4 Nov 2011 6:31 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Everything in the examples are part of the download. If it's not part of the library (like ItemSelector and MultiSelect) then it is going to be housed in the examples/ux/ folder. Look under the form folder there. You could have looked at the source of the example and found them that way also.Mitchell Simoens @LikelyMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
5 Nov 2011 7:50 PM #3
Thank you very much! But I am wondering why MultiSelect item is not provided out of the box and as part of standard distribution just like any other component like button, textfield...Is there any particular reason for it.
Your response is highly appreciated.
5 Nov 2011 9:04 PM #4
There can be all sorts of reasons why components are included as examples rather than as parts of the library itself. Usually it's because the components don't have quite the same level of polish, configurability and extensibility as the rest of the library. Rather than refuse to release useful components on those grounds they are included as official extensions. Many of these components get tidied up and promoted to the main library over time.
I would suspect this is the reason in the case of those two components.
Personally I wouldn't be surprised if MultiSelect gets pulled into the main library at some point. Visually it's very clean and it complements the existing form fields nicely. ItemSelector, on the other hand, strikes me as a pragmatic solution to a difficult problem but not one that would sit comfortably in the library. It's just a bit too clunky.