Thanks Andy,
I hadn't thought about the generated IDs. I would still love to be able to do it (accepting the responsibility of explicitly naming things, etc.). Or maybe we could call a listener on another page that won't take so long to render? There is probably another problem with forwarding
I'm not planning on tackling it at all...Or, if I do it will be the last thing I think about. The tacos-like ResponseBuilder infrastructure should provide us enough of a protective layer that we can add it in when it's ready. (ie Howard had mentioned ideas on how to implement this, maybe he'll have
>From Michael Waluk <[EMAIL PROTECTED]>:
> Hi,
> It seems like DojoResponseBuilder's updateComponentsDirect method could be
> changed to avoid calling render on unecessary components (it is doing so
> with the NullWriter now).
The problem is that if you don't call render on those 'unnecessary'
Hi,
It seems like DojoResponseBuilder's updateComponentsDirect method could be changed to avoid calling render on unecessary components (it is doing so with the NullWriter now). For example, if checkComponentContainers would return null for components that don't have PartialForBean containers it
Yes this issue has been thought about a great deal. It ~might~ happen in tapestry4.1, will definitely happen in tapestry5. I don't know which yet. jesseOn 2/23/06,
Jonathan Bullkich <[EMAIL PROTECTED]> wrote:
Hi,
I'm
working with tacos4-beta-1 and I'd like to know some details abo
Hi,
I'm
working with tacos4-beta-1 and I'd like to know some details about the status
of the direct parameter:
Right
now it's not implemented, all components except the AjaxDirectLink ignore it,
also,
there's a TODO comment in DojoResponseBuilder to handle the order in which component
