OK, maybe I see the reason for firing the request another time. It is
about the pagination if my list result (many entries) spans several
pages -> it is far from obvious to let javascript know how to order this...
manuel aldana schrieb:
> I really like the grid component. Especially the built-in ordering
> (clicking on column headers).
>
> what I miss is that javascript is not used when ordering the tables,
> at each click a complete HTTP request is fired. The data itself is not
> changed so another server call wouldn't be necessary. I at least did
> not find a javascript enable parameter.
>
> If it is not supported yet, maybe this could be a nice improvement for
> this component. For non-JS clients maybe there could even be a
> fallback to standard HTTP request style.
>
> Apart from that why was grid-component not desinged to use div-style
> (vs. tables) for row layout? maybe due to browser compability
> (especially older IEs)?
>
--
manuel aldana
aldana@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
|