| From: |
"JIRA (on behalf of Gregory Joseph)" <dev-list@magnolia.info> |
| Subject: |
[JIRA] Commented: (MAGNOLIA-2281) Import paragraphCollections from multiple modules into one paragraph collection |
| Date: |
Wed, 23 Jul 2008 14:23:13 +0200 (CEST) |
| To: |
dev-list@magnolia.info |
|
 |
|
[ http://jira.magnolia.info/browse/MAGNOLIA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222#action_17222 ]
Gregory Joseph commented on MAGNOLIA-2281:
------------------------------------------
Keep in mind that the helper bean in samples is just that, a sample. Before introducing this, the sample templates simply showed that you could have a comma separated list of paragraphs to be shown.
The core of the issue is that there is no single silver solution that will satisfy all scenarios. In certain templates or sections of templates, you'll want to only have a limited set of paragraphs, and a different set for other templates. (because authors don't want to have to search for the right paragraph, or because you want to precisely control what can be added where)
> Import paragraphCollections from multiple modules into one paragraph collection
> -------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2281
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2281
> Project: Magnolia
> Issue Type: Improvement
> Affects Versions: 3.6.1
> Reporter: Vasko Gjurovski
> Assignee: Boris Kraft
> Priority: Minor
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Currently the mechanism for importing module specific paragraph collections (js and css files as well) is to define the Helper bean and import it into the head of the template via <jsp:useBean.... If we want to import paragraph collections (js and css files as well) we should make multiple <jsp:useBean.. imports along with the js and css importing for each module. This leads to a lot of problems when we have something like 20 modules (for example I need each paragraph to be a single module so I can vary them into different applications) which would lead in to a mess in the code. I am suggesting to make some kind of mechanism that will gather the paragraph collections (js and css as well) from all modules (if they have it) and use them like one collection. I have an idea how to solve this, but needed a approval that it has not been looked at yet and that nobody has tried anything similar, and also, that this agrees with your perspectives and ideas for the modules.
> Best Regards,
> Vasko Gjurovski
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|