Hi!
From an Object oriented aspect you are coupling components to particular pages,
when I understand you correctly. This is for my personal opinion a wrong
design. Can't you not just pass the additional info as parameter from your page
to your component (as Taha suggested it)?
Or are you displaying commen/shared info? Maybe tapestry's "layout" might be a
solution for you?
Jens
Sent from my iPhone
On 12.12.2012, at 06:00, Taha Siddiqi <tawus.tapes...@gmail.com> wrote:
> Hi Bogdan
>
> No sure if I understand you question correctly. From what I understand you
> can use block parameters or <t:body/>
>
> regards
> Taha
>
> On Dec 12, 2012, at 10:22 AM, bogdan_cm wrote:
>
>> Hello everyone,
>> How can I allow "Page" information to be part of the component markup
>> output? Take for example the zone component:
>> <t:zone t:id="someId" id="pageId"> --> component
>> this is the time on day ${timeOfDay} -> this value comes from the Page
>> containing the component
>> </t:zone>
>>
>> When I write my own component, how can I pass additional "data" to be
>> included in the rendering of this component?
>>
>> I would like to write:
>> <t:myComponent>
>> maybe a loop here that would read a list in the Page containing the
>> component, and display it.
>> </t:myComponent>
>>
>>
>> Thank you,
>> Bogdan.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://tapestry.1045711.n5.nabble.com/Component-that-displays-additional-containing-Page-markup-tp5718622.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
