Posted by kaizerking on January 31, 2013 at 4:23pm
3 followers
| Project: | Simple hierarchical select |
| Version: | 7.x-1.5 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I am not sure if this request should be made here or chosen module
chosen as renderer for Simple hierarchical select will be great
feel free to move this to chosen if this doesn't belong here.
Comments
#1
Uhm, how should this look like?
An autocomplete textfield ("chosen") for each level instead of the dropdowns?
#2
Ah wait.
I'll test and try to apply chosen to the created elements. If this will work there will be an integration, otherwise it will be another "won't fix" :(.
#3
Chosen works for select lists as well as autocomplete, also supports multiple values,Auto complete confuses people for hierarchical selection
drop down Select list support will be good
once we install 'chosen' the option is available for all autocomplete fields and select list fields.
you are the best judge how you want to implement this
#4
I will not reveal too much, but ... the integration with chosen is committed to 7.x-1.x-dev :)
After installing Chosen all dropdowns created by Simple hierarchical select (mathing the settings of Chosen) are transformed into Chosen-elements (dropdown with search field).
If you want to exclude the elements created by Simple hierarchical select you can use the selector
select:visible:not(.shs-select)in the configuration of Chosen.You can test the new feature by using the code from git or wait some hours for the next development release.
#5
i git cloned it and tested
1.i don't see 'apply chosen to this field 'option i think users should be given an option everyone may not use chosen
2. only the top most is rendered as chosen element, but very beautiful isn't it? incidentally i have 178 values in that field a simple select wouldn't have helped
3. inline alignment disturbed i.e they are one below the other rater than side wise
pl see screen shot
#6
sorry! forgot to attach png screen shots
#7
Ah, I forgot to mention that the integration is built on top of chosen-7.x-2.x.
Nevertheless an option "apply chosen to this field" would be a good idea.
#8
I've added the per-field option and extended the README.txt to make clear you'll need at least 7.x-2.x.
Did you test it with 7.x-1.x?
Inline alignment of the fields needs to be done on a per-theme base since I'm no fan of overriding CSS declarations for elements a module did not create itself ;).
#9
great ,It is working!! thanks
#10
I've extended the integration so you can decide (on a per-field base) to
* always render the elements with chosen (even if the field would not match configuration of chosen)
* never render the elements with chosen (even if the field would match configuration of chosen)
* let chosen decide whether to render it (default behavior)
As a bonus this works for Views exposed filters, too :)
#11
Wow!!great.
Thank you for all of your efforts.
#12
Built into version 7.x-1.5.
#13
Automatically closed -- issue fixed for 2 weeks with no activity.