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

Kalle Korhonen reopened TAP5-1606:
----------------------------------

      Assignee:     (was: Howard M. Lewis Ship)

Let's make another try at this. There was a continued discussion on the mailing 
list on this topic and people see value in the concept. There was more support 
for a mixin that would target specific types of embedded components rather than 
ids of components that was deemed as too brittle.

> EmbeddedMixin concept
> ---------------------
>
>                 Key: TAP5-1606
>                 URL: https://issues.apache.org/jira/browse/TAP5-1606
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Dragan Sahpaski
>            Priority: Minor
>              Labels: mixin
>         Attachments: EmbeddedMixin patch.diff
>
>
> The EmbeddedMixin concept allows applying mixins on embedded components of an 
> existing component.
> Usage scenario:
> A mixin can have embedded mixins defined with the new @EmbeddedMixin 
> annotation.
> A motivational demo can be found here 
> http://dragansah.com/demoapp/embeddedmixinexamples
> Usage example:
> <t:grid t:mixins="mixinForGrid" />
> public class MixinForGrid
> {
>         // apply the MixinForGridCell mixin to the rows.gridCell subcomponent 
> of the grid
>         @EmbeddedMixin(componentId="rows.gridCell")
>         private MixinForGridCell mixinForGridcell;
>         // render phases on the grid
>         void beginRender()
>         {
>         }
> }
> public class MixinForGridCell
> {
>         // render phase on gridCell
>         void beginRender()
>         {
>         }
> }

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to