Any time you change the number of components in the form without rerendering
the page, you will invalidate the form. There is a field within the page
that stores the number of components that will need to be changed (and as of
Tapestry 4.0, I think that field may now be DataSqueezed, someone else can
set me straight on that one).
----- Original Message -----
From: "Patrick Casey" <[EMAIL PROTECTED]>
To: "'Tapestry users'" <[email protected]>
Sent: Monday, August 15, 2005 1:49 PM
Subject: RE: More Partial Form Stuff
Thanks Viktor, that helped reduce the amount of rendering I'm doing.
Unfortunately, I ran into a different problem that I'm not sure is
solvable.
I have two forms, one big one, one little one.
I use the small partial form to update a div within the big form.
I then (later) submit the big form.
I get a stale link because the big form has a different widget count
than it did when originally rendered.
I think for what I'm doing I'm just not going to be able to use this
implementation of partial form unfortunately. Now that I understand it
better, I can see uses for it, but it doesn't match up well with my use
case.
--- Pat
-----Original Message-----
From: Viktor Szathmary [mailto:[EMAIL PROTECTED]
Sent: Monday, August 15, 2005 9:03 AM
To: Tapestry users
Subject: Re: More Partial Form Stuff
hello,
On 8/15/05, Patrick Casey <[EMAIL PROTECTED]> wrote:
>
>
> mistaken (which wouldn't be the first time), this particular AJAX
> implementation isn't going to save me anything on page render time
because
> even if I'm only updating a small div in the middle of the form,
Tapestry
> still has to render the entire form and return it. So the only thing
> I'm
> really saving on is the "screen flicker" associated with a complete
redraw.
> In terms of server side resources and network resources, I'm still A)
> building the whole form and B) sending the whole form.
That is generally true - with the tapestry rendering lifecycle you
can't jump in to the middle of the rendition cycle, things could
easily break... However, Tacos will skip rendering for Parts that have
optimize="true" set and are not needed for the current request. Read
the docs on the optimize parameter.
hope this helps,
viktor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
