Thanks for the feedback - I believe I have immplemented the strategy
described using the ComponentSource method (as opposed to using blocks) in
the previous thread. The problem I'm seeing is that I have a component that
is rendered 3 times on a page with a different panel context
An example of on
On Mon, 21 Jun 2010 16:06:38 -0300, Pierce Wetter
wrote:
More broadly speaking has anyone managed to implement a dashboard style
application (i.e.layouts/panels) and what is the correct pattern to use?
I'm not a T5 expert, but I think you want to use a delegate.
A very recent thread in t
>
>
> More broadly speaking has anyone managed to implement a dashboard style
> application (i.e.layouts/panels) and what is the correct pattern to use?
I'm not a T5 expert, but I think you want to use a delegate.
Pierce
-
I have an existing T5 application that contains approx. 25 components. In
it's current "stable" version the arrangement of these components across
pages is pre-defined and everything works fine. Given Tapestry's component
approach it comes as no suprise that users are now requesting a more
flexibl
