On 4/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>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'
components, you will end up with a different page 'state' when you
render the component that interests you (both client + server state).
For instance, assume you have a component X that includes a
[EMAIL PROTECTED], and that you include X twice in your page.
The first link will get id="link" and the second id="link_0".
Now, if you update directly the second one, it will generate
id="link" and the page will probably misbehave.
This exact problem can appear in many other different forms,
even when direct="false". I someone is interested, we can talk on
how these problems can come up in another thread, or perhaps
write a nice document so that tacos users are aware.
Also, I'm not yet sure how jesse is planning to tackle this in Tapestry 4.1
but it may have to be discussed there too.
> Another (less important) question: Without direct="true" working I had some
> lamer ideas like putting my component on a 2nd page and either call its
> listener on that page (therefore the page refresh only rendered the 1
> component) or call the listener on the original page but use
> cycle.activate()
> to forward to the new 2nd page for rendering the response (even goofier). I
> looked at AjaxDirectServiceImpl and was wondering why the
> "checkNewPageActivated" method treats a forward like a redirect?
>
See http://tacoscomponents.jot.com/BugReporter/Bug35
for a talk on this. Another thought was to have the new page
rendered in the same cycle and have the ajax direct service return all of it +
the client _javascript_ would then replace it all.
Are there any other options?
> Thanks,
> Michael
>
>
> On 2/23/06, Jesse Kuhnert <[EMAIL PROTECTED] > wrote:
> >
> > 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.
> >
> >
> > jesse
> >
> >
> > On 2/23/06, Jonathan Bullkich <[EMAIL PROTECTED]> wrote:
> > >
> > > 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 components
> > >
> > > are rendered.
> > >
> > > Are there any plans to implement it?
> > >
> > >
> > >
> > > Another thing, the way that it's implemented right now, even when the
> > > direct parameter is true,
> > >
> > > the rendering is performed for every component, with the NullWriter, but
> > > still, all the server
> > >
> > > side work, to get each component value is performed.
> > >
> > > I'd really like that when the direct parameter is true, that only the
> > > components in the updateComponents
> > >
> > > List will perform their server side logic.
> > >
> > > Have you thought about this issue?
> > >
> > >
> > >
> > > Thanks,
> > >
> > >
> > >
> > > Jonathan
> > >
> >
> >
>
--
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://opennotion.com
