Ok, but I need to populate the form content with ajax. I could edit 1 of
50 elements, and i don't want to load in all of the editable data until
it's selected. The problem as I see it is less that the dialog is
shown/hidden, but that the form components are essentially detached from
the page's form once they are updated via ajax.
FYI I've solved this by reworking my border component so that I can have
more than one form per page. The only drawback is that if I change the
enabled/disabled status of an element (click checkbox), then load the
dialog and save that, my enable/disable change is not registered, as the
page's form is not submitted.
Anyway, I think it's a small price to pay, however it would have been
nice if tapestry could maintain the link with updated form components as
described.
Thanks for the help Miguel.
Miguel Angel Hernández wrote:
The trick is that the dialog its always inside the Form, as a hidden
part of
the dom i,e: visibility='hidden':
<div
id="ognl:contenedorId"
jwcid="@Any"
style="position:absolute;visibility:hidden;z-index: 555"
>
<span jwcid="@RenderBody"/>
</div>
Whenever I need such dialog to show(and render or populate its
bindings) I
update the @Any component,
and change the visibility and position via javascript (it has to be done
with js to paint it right).
regards,
Miguel
On 5/30/07, Paul Stanton <[EMAIL PROTECTED]> wrote:
how did you handle population of the dialog form portion?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
