When you deploy views, there is a single drop down for the view you're adding to your plan. This sucks because
1) If you have a lot of views, using the drop down is really tedious
2) You can only add one view at a time, so if you're adding a lot of views to a plan, there's a lot of back and forth
I have considered checkboxes/multiple select boxes, but neither are ideal if you have 30+ views which is not unusual. Perhaps some jQuery whizbangery would help here, with a fallback to multiple select when there's no javascript. If someone has any JQ experience have at it. This could also be used in the content_copy_deploy.module which uses the same UI (and I'm sure it will be needed plenty of other places too.)
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | hs_support_for_deployment_ui.patch | 2.76 KB | wim leers |
| #9 | hs_support_for_deployment_ui.patch | 4.1 KB | wim leers |
Comments
Comment #1
wim leersPlease check out the multiple select demos of my Hierarchical Select form element over here: http://wimleers.com/demo/hierarchical-select. I think that's what you're looking for (but without the hierarchical stuff)?
Comment #2
gddThat is freaking cool, it's exactly the kind of thing that would be great. Thanks for pointing it out (or, feel free to write a patch!)
Comment #3
wim leersIt's virtually no work, so when I find the time, I'll get it done. Don't expect it soon though, since I'm in the middle of my exam period.
Comment #4
gddI've implemented this with a multi-select box for now, I'll revisit it in the next rev (unless WimLeers wants to jump in after the beta gets released)
Comment #5
wim leersI've been extremely busy with university projects. I won't have time before the beginning of July. You *will* get this in July though ;) :).
Comment #6
wim leersBeta 1 of HS 3 is out. I'll add support for the Views deployment UI soon (i.e. in a couple of days).
Are there any other areas in the Deploy module where you could use it?
Will you add a dependency on Hierarchical Select or do you want it to fall back to a normal select?
Comment #7
gddyes the same issue exists in content_copy_deploy.module
Thanks a lot!
Comment #8
wim leersWorking on this right now! :)
Comment #9
wim leersWoot, already done! This was super easy to support, because there isn't any kind of hierarchy here, and I just wrote a generic "Flat List" implementation that simply accepts an array of options.
I added it for both the views_deploy and content_copy_deploy modules.
I've added dependencies on this module (hs_flatlist, which in turn depends on hierarchical_select), but it could be written as a "progressive enhancement": only use HS when it's present. That's up to you to decide.
Note: you have to use CVS HEAD for this, this has been done *after* beta 2 of HS 3. If you wait long enough, the dev tarball will also include this (look for the file
modules/hs_flatlist.module).Comment #10
gddAck, for some reason I did not get an email notification of this! I will look at it soon. Thanks!
Comment #11
wim leersHave you been able to give this a look yet? :)
Comment #12
gddThis is really nice, much better than using a multiple select list. Thanks for the patch! I think I would like to see it work as a progressive enhancement so I don't have to make HS a dependency. Installing and running Deploy is reasonably complicated already and I just don't want to make it any more so.
Otherwise this is awesome!
Comment #13
wim leersNo problem, I understand :)
I just edited the patch, so I'm not 100% sure this patch will work. If it doesn't work, you can just copy/paste the missing parts. Even less changes required this time :)
Comment #14
gddTweaked a little and commited! Thanks much.
Comment #15
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.