Hm... I would shy away from that one, due to the nuance that "block"
has in tapestry.
At least for me, saying "FormBlock" would suggest some piece of a form
that can be randomly plugged into various other forms... like a bean
block contribution.
FormFragment is ok, but I'm with Ulrich that the name ought to suggest
the conditional nature of the component.
Robert
On Feb 18, 2008, at 2/184:52 PM , Igor Drobiazko wrote:
FormBlock would be another possibility
On Feb 18, 2008 9:35 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I've been continuing to work on Ajax/Form functionality.
Last couple of days has been on a component I'm calling a SubForm.
A SubForm is part of a Form that is conditionally visible.
It is always rendered, but a trigger (typically a checkbox) makes it
visible or hidden.
Form controls on the client side are only validated if visible.
Actually, "deep visible", meaning that they are visible and that
their
containers are recursively visible.
On submission, a hidden field for each SubForm tracks its deep
visibility.
On the server side, the form submission for components enclosed by
the
SubForm only occurs when the SubForm is visible on the client side.
If the SubForm is invisible, then no form processing for those
components occur.
It's all working pretty nicely, but I'm not sure "SubForm" is the
right
name.
Other idea:
- Section
- FormSection
- FormConditional
- ???
I'll be committing changes later this afternoon so nows a great time
to get the naming right.
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best regards,
Igor Drobiazko
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
