[MAGNOLIA-3830] Multiselect variation of other dialogs then "info.magnolia.cms.gui.dialog.DialogMultiSelect" Created: 12/Sep/11 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface, fckeditor, gui |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Per Andersson [X] (Inactive) | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Hi, There is a feature in Liferay that I miss in Magnolia. Liferay gives the developers power to have a dialog or a combination of dialogs marked as multiple. Let's try a scenario we have where I work. We have a very specific article component which contains the following dialogs: The freemarker file looks like this: standardArticle.ftl ${image1} - ${text1}<br />
${image2} - ${text2}<br />
${image3} - ${text3}<br />
There are two big downsides with this approach that I can see straight ahead. The first one is that we need to do a "release" if we want to increase the number of Image-Text combinations. The second one is that editor interface becomes very bloated (especially if they only want to use one combination (Image1 and Text1) and not the other fields). What I would like to have is the possibility to tell magnolia that I want the "Image" and "Text" dialog combination to be "multiple", i.e. you can add a dynamic amount of rows on the fly. Of course it would be nice for it to work in Blossom since we use that for many of our paragraphs. If this type of feature is implemented, then the dialog configuration might look like this instead: The freemarker file looks like this: standardArticle.ftl <#list content.imageText?children as imgtxt>
${imgtxt.image} - ${imgtxt.text}<br />
</#list>
I've already made my own bastardized version of the DialogMultiSelect class (and it's only tested using Blossom as of yet) but I don't really know much about Magnolia yet so the result is pretty much a hack. Also - since it's a variation of the original DialogMultiSelect class it doesn't work with the FckEditor because it is very javascript dependent. I might be able to include my version so that you can look at it (But I have to remove some domain specific information from the source code before I can include it) |
| Comments |
| Comment by Magnolia International [ 10/Nov/11 ] |
|
Per, I seem to remember we had a look at this in the past (and was sure there was another similar report, just can't find it). My feeling is that it wasn't something we'd be able to do nicely and quickly. Specific hacks are doable, but a general solution seemed complicated... and we postponed it until we could revamp the complete UI. Now this is actually becoming closer to a reality with 5.0, I wouldn't get my hopes high up this gets fixed in the meantime. Of course, if you have patches against the current code, we'll look into it ! But hopefully, this kind of thing will be much simpler with 5.0 ! |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |