Chakra words reminds me of the interesting idea for components to have
their independent activation context. That page is not aware of.
In this case the component encapsulates the knowledge about specific
url parameters that it needs. And can be reused on different pages
without altering them. For example imagine a custom pager component
that needs parameter "pageNum".
I use a somewhat similar solution using @Environmental inside Mixins
that stores data in request parameters.
("?pageNum=3&anotherParam=3.333")
On Mon, Sep 14, 2009 at 8:15 PM, Howard Lewis Ship <hls...@gmail.com> wrote:
> Otho is exactly right here. Each piece of Tapestry has its purpose, and
> pages act as a bridge between the client and the components within the page.
>
> On Mon, Sep 14, 2009 at 4:13 AM, Otho <taa...@googlemail.com> wrote:
>
>> I wouldn't couple a component so tightly to a specific page. If you need to
>> pass certain bits of information you can also use component parameters from
>> within the page.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
