On the screen for inserting Rendered bean there is field called Delta. It's not useful from the UX point, because it's not clear what it is - user doesn't see of fill this value during bean creation (I know about issue #1365656: Edit machine_code in UI, which will be useful in any case).
Even so, I'm suggesting to make this field as select list of existing beans (administrative label as value and bean delta as key for select options). This will improve UX for site administrators, which aren't so familiar with drupal terminology and which don't know where they could pick the delta of the bean block.
Here is the patch, which implement this feature.
Thanks,
Artem.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | bean_list.png | 15.96 KB | berdyshev |
| #3 | bean_panels_list_of_beans-2.patch | 3.1 KB | berdyshev |
| #3 | bean_panels_before.png | 11.53 KB | berdyshev |
| #3 | bean_panels_single_link.patch | 457 bytes | berdyshev |
| #3 | bean_panels_single_link.png | 12.26 KB | berdyshev |
Comments
Comment #0.0
berdyshev commentedUpdated issue summary.
Comment #1
berdyshev commentedAnother variant is to replace one link "Rendered bean" with set of links for each bean. It will looks like list of views or core blocks.
Here is the patch for this one. We can choose one better solution.
Comment #2
andypostPlease, provide a screenshots of changes because this patch introduces UI changes
Comment #3
berdyshev commentedSome screenshots for those changes
1. Changing delta field to bean select field.
Currently (in bean_panels 7.x-1.1):
After applying first patch (bean_panels_delta_to_select.patch):
2. Also it will be better to move "Rendered bean" link to list of single links (bean_panels_single_link.patch) like this:
3. Replacing one link "Rendered bean" to list of links (bean label plus bean type).
Bean module now creates the new tab with only one option (link) - "Rendered bean"
After applying patch bean_panels_list_of_beans-2.patch (improved version of #1) Bean section will looks like this:
Comment #4
andypostSuppose all changes makes a lot of sense
Comment #5
berdyshev commented@andypost, thanks.
But I want to note that variant 1+2 and 3 are mutually exclusive.
And the 3 variant requires the upgrade path, because previously created bean panes will be incompatible with new solution and won't be displayed. But I don't sure how to implement this upgrade path.
Comment #6
larowlanHi
The intent of keeping this loose was so you could ship a panel/page manager page without the bean, keeping configuration (the panel content) separate from the content (the bean).
In light of this I think the select option keeps this separation. If you want to just output the bean, you can do so using the existing block ctools content type which already provides the beans, albeit without being able to choose the view mode, but there nonetheless.
Also, the select option doesn't require an upgrade path.
Lee
Comment #7
larowlanCommitted patch from issue summary as b168e17, thanks!
Comment #8.0
(not verified) commentedUpdated issue summary.