> I guess that part of your solution is to use blocks and the Delegate
> component:
> http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry5
>/corelib/components/Delegate.html.
Thanks again :-)
I am trying to come up with a solution, but have to admit that my
understanding of the tapestry concepts are just not good enough :/
Right now I have a "portal" component that should hold one or more
"portalColumn" which in turn should hold one or more "portlet"s. (note: this
does not refer to jsr-168, but is just my naming).
Is it right that there is no possibility to dynamically define at runtime how
many portlet columns are displayed? ( I would love to make this
configurable). And then do I need to define every possible portlet inside a
block somewhere on a page - or is it enough to have the components around?
Problem is that I do not know in which portletColumn my portlet is displayed
in. Is there some example or documentation of how such things could be done
with tapestry's "static structure, dynamic behaviour" philosophy?
The Delegate and Block components are looking useful - but right now I don't
have a clue how to use them to solve my problem.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
