tnx a lot Alejandro!
this is exactly what I was looking for, block/renderblock components
combined with EventListener can be really powerful stuff but I didn't
realize it until I read your example.
It's also very interesting the way you use that Editors page as a "block
component repository" an
Hi Guys,
I don't know if this is what are you looking for but here is how we
handle our "dynamic" components at Trails.
First we have a page which contains what we call "editors" (our
"dynamic" components):
http://svn.codehaus.org/trails/trunk/trails/modules/trails-core/src/main/resources/org/tr
did you find any cleaner way to do this?
I think this problem is not just related to "one page applications" but
apply also to any page/component that depending un user actions must show
different enough content (unless one wants to go with EventListener and a
long ugly list of IF components...)
Well I want to make a single page application, so componentns (the
body part of a page)
will be injected as reference by hivemind into different jars.
Playng a bit with Tapestry src I've found a better way to do this, but
I need some more testing (assets, listeners, etc).
I'm investigating on th
Hmm I'm not sure. It doesn't look right but it's possible. Wouldn't
@Block be the easiest way to do it? Or different instances of IRender ?
On 5/31/07, Andrea Chiumenti <[EMAIL PROTECTED]> wrote:
Is it right to do this ?
public IRender getDynaComp() {
IRequestCycle cycle =
getEngine
Is it right to do this ?
public IRender getDynaComp() {
IRequestCycle cycle = getEngine().getInfrastructure().getRequestCycle();
IWorkerRender result;
if ((cycle.getParameter("body") != null) &&
(!(cycle.getParameter("body").equals(""))) ) {
result = from a service
