On Fri, 22 Jul 2011 09:12:33 -0300, George Christman
wrote:
Thanks everyone. I only used the title as a simple example to figure out
if components were bi directional.
Components aren't bidirectional. Bindings (used in component parameters)
can be bidirectional. The prop binding is bidir
't have to
replicate code between the create and update pages.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-property-into-page-tp4620541p4622828.html
Sent from the Tapestry - User mailing list archiv
Just as a side note: Environmental is not the only way. Component parameters
are actually bidirectional. For example property bindings are writable. A
component parameter is not limited to provide values for components. It may
be used to populate a value from the component to its container. A good
Hi!
On Thu, 21 Jul 2011 17:48:37 -0300, Josh Canfield
wrote:
I'm not sure how this helps the OPs problem though.
BeginRender for your component is going to happen after the layout
component has started rendering, and already output the title. Right?
Right!
t:mycomponent won't get
> You'll need to use the Environmental service in your page and add some
> custom object on it, typically in @BeginRender. Then, in your component, you
> invoke some method in this object. In the page, in some event after
> @BeginRender, you get the value back.
I'm not sure how this helps the OPs
ah okay, Thanks
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-property-into-page-tp4620541p4620616.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe
On Thu, 21 Jul 2011 15:32:27 -0300, George Christman
wrote:
Yes, in my example I'm trying to pass a title generated in the page
component back to the layout component.
Tapestry's philosophy is that components (including pages) are and should
be black boxes, so the normal flow is from top
Yes, in my example I'm trying to pass a title generated in the page component
back to the layout component.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pass-component-property-into-page-tp4620541p4620575.html
Sent from the Tapestry - User mailing list archi
vate String title;
>
>
>
>
> ***Layout component***
>
>
> @Parameter(required = true)
> @Property
> private String title;
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Pass-comp
Does anybody know how to pass a prop:value from the component back to the
page? I know how to do this very easily from the page to the component, just
not in reverse.
I tried
***Custom Component***
http://tapestry.1045711.n5.nabble.com/Pass-component-property-into-page-tp4620541p4620541.html
10 matches
Mail list logo
