Is it possible to have a grid with one form for each row? All examples
I see everywhere have a single form wrapping grid inside. For my
functional spec, which requires Update/Remove buttons on each row, a
single form has some unwanted implications such as validating other
rows on submission from only one row (such as non-numeric input into a
numeric field).

When I do this:

<t:grid...
 <t:form...
 </t:form>
</t:grid>

All cell overrides (<t:parameter) inside the form are not taken into effect.

Lastly, assuming this can be done, I would need <t:errors outside the
form because error messages must be displayed in the same common
location (at the top of the grid, whatever). But errors outside of
form is not allowed. So do I update zone on form submit to handle
errors thru ajax?

I'm making a progress on my project with Tapestry, which is to rewrite
a working Struts website without a single UI change. Great framework
for the basics, but from what I have experienced so far, the learning
curve to override and customize seemingly simple things is just
astronomical. The framework is great at getting things done quickly
with defaults, but the minute you want to override some behavior
Tapestry seems to be very rigid.

My boss, to whom I successfully sold the idea of rewriting our website
from Struts 1 to Tapestry 5 is starting to have second doubts due to
inflexibility of Tapestry on concepts that are simple, and should be
simple but are not. Above grid is one such example. Ajax, was another
big one (although that I got solved after weeks of pounding my head
against the wall)..

I am little frustrated, I am sorry but that is first hand experience.
In any case, any help on the grid issue would be highly appreciated.

Adam

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to