forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sina K. Heshmati (JIRA)" <>
Subject [jira] Commented: (FOR-1059) Reusable Panels for Core Themes
Date Tue, 18 Dec 2007 15:38:43 GMT


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"/>
    <jx:import uri="cocoon://prepare.panels.pelt-html.footer"/>

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:
>             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]

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message