You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2008/10/16 19:01:44 UTC

[jira] Updated: (TAP5-74) Provide a way that a component sub-class can merge its template with that of its container

     [ https://issues.apache.org/jira/browse/TAP5-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-74:
-------------------------------------

    Issue Type: New Feature  (was: Bug)

> Provide a way that a component sub-class can merge its template with that of its container
> ------------------------------------------------------------------------------------------
>
>                 Key: TAP5-74
>                 URL: https://issues.apache.org/jira/browse/TAP5-74
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>
> This is an idea I've picked up from Wicket; which has a special element, similar to Tapestry t:body, but used to indicate where the child component's template should go.  In Wicket, pages are often given a common L&F not by the use of a common component, but by extending a common base class, and mixing the base class' template with the sub-class.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org