[
http://jira.magnolia.info/browse/MAGNOLIA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223#action_17223
]
Vasko Gjurovski commented on MAGNOLIA-2281:
-------------------------------------------
Yes, I have thought of that and the answer is simple: you can always have a
different paragraph collections for different purposes which you can as well
define in the module. For example, if you have par1 and par2 from module1 and
par3 and par4 from module2, you can make col1 which includes par1 and par3 and
col2 which includes par2 and par4. And of course you can have any combination
you like, as long as you define the same paragraphCollection name in all the
modules (or include both paragrapCollections comma separated ;) ). After that
you can use the different paragraphCollection in different templates of
sections of templates.
So my main point not to avoid the paragraphCollection node in config but to
simply manage a more simple way of collecting ALL the paragraphs and then
distributing them into the paragraphCollections as you wish.
Then again, perhaps there should be some part in adminCentral that can manage
the paragraphCollections globaly (or per site, which has not yet been defined
in Magnolia), but thats another story... :)
> 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
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
