[
http://jira.magnolia-cms.com/browse/MGNLSTK-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivian Steller updated MGNLSTK-699:
-----------------------------------
Description:
Currently C2B is not used to instantiate the site's prototype, which is sad.
Developers expect being able e.g. to use the "class" nodedata to switch the
implementation of an area (e.g. the header). Instead (if you're lucky, e.g. for
header, but not for something deeper in the hierarchy) one needs to set the
implementation class in a custom module's properties to be able to switch the
implementation.
Note also, that the objects created in DefaultSTKTemplateConfiguration are not
taken into account at all. They're only used for merging the configurations
which seems to be odd as well.
I'd like to suggest using C2B for instantiating the merged template
configuration (merge based on Content objects not beans).
was:
Currently C2B is not used to instantiate the site's prototype, which is sad.
Developers expect being able e.g. to use the "class" nodedata to switch the
implementation of an area (e.g. the header). Instead (if you're lucky, e.g. for
header, but not for something deeper in the hierarchy) one needs to override a
method in DefaultSTKTemplateConfiguration (and switch the implementation of
STKTemplateConfiguration in your custom module) to be able to switch the
implementation. In DefaultSTKTemplateConfiguration any "root area" seems to
instantiated without any factory pattern, which could additionally be improved.
I'd like to suggest using C2B for instantiating the merged template
configuration.
> Use Content2Bean to instantiate a site's template prototype
> -----------------------------------------------------------
>
> Key: MGNLSTK-699
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-699
> Project: Magnolia Standard Templating Kit
> Issue Type: Improvement
> Components: templates
> Affects Versions: 1.3.5
> Reporter: Vivian Steller
> Assignee: Philipp Bärfuss
> Priority: Critical
>
> Currently C2B is not used to instantiate the site's prototype, which is sad.
> Developers expect being able e.g. to use the "class" nodedata to switch the
> implementation of an area (e.g. the header). Instead (if you're lucky, e.g.
> for header, but not for something deeper in the hierarchy) one needs to set
> the implementation class in a custom module's properties to be able to switch
> the implementation.
> Note also, that the objects created in DefaultSTKTemplateConfiguration are
> not taken into account at all. They're only used for merging the
> configurations which seems to be odd as well.
> I'd like to suggest using C2B for instantiating the merged template
> configuration (merge based on Content objects not beans).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
