14 Mar 2013 9:40 AM #1
As I didn't like available extensions, I've extended Ext.field.Select widget and added the multiselect feature. Works as a single or multi select field.
It can easily extend Ext.field.Text if to take the missing code from Ext.field.Select and add it to Ux.field.Multiselect.
Github repository: https://github.com/vadimpopa/Ux.field.Multiselect
Tested&works on ST 2.1 , 2.2
Multiselect field example image:
Screen Shot 2013-03-14 at 7.09.29 PM.png
EDIT: usePicker config won't work as it is always used a list on both tablets and phones
Last edited by vadimv; 10 May 2013 at 6:02 AM. Reason: added note aboute usePicker
16 Mar 2013 12:50 PM #2
- Join Date
- Mar 2007
- St. Louis, MO
- Vote Rating
Without using it, what happens when someone is on a phone and the developer wants to use an array of values?Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
http://www.JSONPLint.com - Source to lint your JSONP!
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 almost in print!
When posting code, please use BBCode's CODE tags.
16 Mar 2013 2:39 PM #3
16 Mar 2013 3:11 PM #4
18 Mar 2013 6:19 AM #5
I think there's a very simular plugin, maybe someone needs an alternative which works on small screens, too:
25 Mar 2013 3:35 AM #6
Took a fast look and seems that on each item's element is attached a button, which at first impression is used only to show the check/uncheck state, IMO is too much, it makes list's DOM bigger but for what....hope I might be wrong....will take a dipper look this days.
And probably the select/cancel button is an optional not useful step for the user, at least if to use it in the app I'm working at, but for others could be useful....
25 Mar 2013 4:09 AM #7
Yeah you're right, every list row has a button. I'm not sure how much this slows the component down, but for really long lists it's definitly a problem, good point!
The buttons in the bottom toolbar are optional and are passed to the component as items of the actionsToolbar.