tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (TAP5-502) Parameter passing between components is not well explain
Date Wed, 04 Mar 2009 18:47:59 GMT

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

Howard M. Lewis Ship reassigned TAP5-502:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> Parameter passing between components is not well explain
> --------------------------------------------------------
>
>                 Key: TAP5-502
>                 URL: https://issues.apache.org/jira/browse/TAP5-502
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 5.0.18
>            Reporter: Francois Armand
>            Assignee: Howard M. Lewis Ship
>
> It seem that the documentation for parameter is milseading. 
> The way parameter are defined and passed between a parent component and its child use
to be really well explained (I think it was in the "Parameter" page, but I'm not sure). It
seems that the introduction text which use to deal with the concept is no more in the Parameter
documentation, what leads to really big miscomprehension from user.
> It would be really great to add again something about that at the beginning of the parameter
page (before the loop example).
> That is the text in the T5 refcard on that topic, which seems quite good:
> ===
> A page binds the parameters of its child components. For example, a TextField properties
> component's value parameter is bound to a property, or property expression, indicating
what object property it will
> read (when rendering) or update (when the containing form is submitted). 
> ===
> And there used to be something about parameter being a conduit, both read and write,
between a component and it's container that was quite nice too. 

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


Mime
View raw message