You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2008/02/27 21:32:07 UTC

[jira] Resolved: (TILES-218) [tiles] Change of scope for tiles

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

Antonio Petrelli resolved TILES-218.
------------------------------------

    Resolution: Duplicate

This is duplicated by TILES-208.

> [tiles] Change of scope for tiles
> ---------------------------------
>
>                 Key: TILES-218
>                 URL: https://issues.apache.org/struts/browse/TILES-218
>             Project: Tiles
>          Issue Type: New Feature
>          Components: tiles-core
>    Affects Versions: 2.0.4
>         Environment: Operating System: All
> Platform: PC
>            Reporter: Chris Erskine
>            Priority: Minor
>             Fix For: 2.1.x
>
>
> I would like to see a parameter added to the tiles definitions which would 
> allow the scope to be changed.  Currently, the scope of a tile definition is 
> only for the current tile where as I would like to make it include all sub-
> tiles.
> I have a layout which includes a top banner, a left menu and the content well.  
> With the current scope, I have to create a tile definition for each tile if I 
> want to use tile parameters within the sub-tiles.  If I have 1 content tile 
> which is used from 5 different pages, each requiring different navigation and 
> top banners, I have to define the 5 master definitions, then 5 definitions each 
> for the left menu, the banner and then the content.  This is a total of 20 
> definitions that will have to be defined.
> On the other hand, if I could change the tile scope to include sub-tiles, I 
> could then have just the 5 master definitions.
> If there are sub-tiles on a sub-tile which also requires different values, the 
> definitions could get carried away very quickly.

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