You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Mck SembWever (Updated) (JIRA)" <ji...@apache.org> on 2011/10/29 14:07:32 UTC

[jira] [Updated] (TILES-539) OptionsRenderer

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

Mck SembWever updated TILES-539:
--------------------------------

    Summary: OptionsRenderer  (was: OptionsDispatchRenderer)
    
> OptionsRenderer
> ---------------
>
>                 Key: TILES-539
>                 URL: https://issues.apache.org/jira/browse/TILES-539
>             Project: Tiles
>          Issue Type: New Feature
>          Components: tiles-extras
>            Reporter: Mck SembWever
>            Assignee: Mck SembWever
>             Fix For: 3.0.x
>
>         Attachments: TILES-539.patch
>
>
> This takes the concept explained http://tech.finn.no/2010/11/04/the-ultimate-view/4/
> It moves the long [...|...|...] pattern that's embedded in the template's value, to a lookup using the syntax
> ${options[name]} 
> where name refers to a list-attribute that contains the list of options.
> The patch here is more to open the discussion.
> Where is the correct place to put such a class?
> Can this be done using just an Evaluator? (It would be nice but it relies on the attempt to super.render(..) )

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira