The key to performance with Grid is to look to the GridDataModel and
provide a smarter caching version that limits the amount of data taken from
the database.
That being said, Grid is an scaffolding component ... much like
BeanEditForm. It is meant to be useful but if a grid view of some form is
e
Hi Antal,
Thanks for your suggestion, I am afraid that i can not use this component
because actually we had existing grid component extends tapestry grid, but
it's helpful because i can take a look to know how to customize grid to
adapt with huge records for increasing peformance.
Thanks again,
D
Hello Duy,
Have a look at the weaves Tapestry 5.x library, it contains a Pagedgrid
component with a custom gridsource which will never query the total number
of rows in a dataset and uses paging to increase performance, especially for
large datasets. We use it to scroll through recordssets of
Thanks for your suggestion. I will take a look on it.
Duy.
On Sun, Dec 22, 2013 at 5:39 PM, François Facon wrote:
> Hi Duy,
>
> Did you have a look at
>
> http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/griddatasources
> ?
> To support access to large data, you will have to pro
Hi Duy,
Did you have a look at
http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/griddatasources
?
To support access to large data, you will have to provide a class that
implement GridDataSource
(
http://tapestry.apache.org/5.3.7/apidocs/org/apache/tapestry5/grid/GridDataSource.htm
