[
https://issues.apache.org/jira/browse/FOR-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552795
]
Sina K. Heshmati commented on FOR-1059:
---------------------------------------
Please do NOT add these patches as it will affect other Forrest instances using
the Dispatcher.
The following is a sample 'pelt-html.panel.xml:'
<forrest:template ...
<jx:import uri="cocoon://prepare.panels.pelt-html.head"/>
<forrest:hook name="container">
<jx:import uri="cocoon://prepare.panels.pelt-html.header"/>
<forrest:hook name="page">
<jx:import uri="cocoon://prepare.panels.pelt-html.leftbar"/>
<jx:import uri="cocoon://prepare.panels.pelt-html.content"/>
</forrest:hook>
<jx:import uri="cocoon://prepare.panels.pelt-html.footer"/>
</forrest:hook>
</forrest:template>
Some Questions
-----------------------
(1) Let's say that a given project does not want to change the views at all,
that is no project-specific panels. How can make sure that the one included in
the core.themes plugin is used? This way, every instance using the Dispatcher
won't be affected.
(2) Should I remove the forrest:hooks from the pelt-html.panel.xml? So as to
make it easier ti add project-specific contracts to the existing views.
> Reusable Panels for Core Themes
> -------------------------------
>
> Key: FOR-1059
> URL: https://issues.apache.org/jira/browse/FOR-1059
> Project: Forrest
> Issue Type: Improvement
> Components: Plugin: themes.core
> Affects Versions: 0.9-dev
> Reporter: Sina K. Heshmati
> Priority: Minor
> Fix For: 0.9-dev
>
> Attachments: FOR-1059-themes-20071218-01.patch,
> FOR-1059-themes-20071218-01.tar.gz
>
>
> It's useful to have reusable panels for each theme [1]. I'm sending the
> html-pelt theme that's been chunked into different templates.
> [1] http://marc.info/?l=forrest-dev&m=119738096213489&w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
