First of all: Overall is Tapestry 5 in general and the the Grid
component in particular an amazing piece of software. So this is *not*
complaints, just an attempt to sort things out, to share my experiences
and check that I understand things correctly.
I have a use case where I'm about to
Alec Leamas wrote:
- The paging policy with a fixed number of numbered pages is hardcoded
and can't be changed. Other policies e. g., overlap between pages
Isn't that something you can handle inside your own GridDataSource? With the
page number, the number of results per page, the number of
Jesper Zedlitz wrote:
Alec Leamas wrote:
- The paging policy with a fixed number of numbered pages is hardcoded
and can't be changed. Other policies e. g., overlap between pages
Isn't that something you can handle inside your own GridDataSource? With the
page number, the number of
There's certainly an issue that if the Grid component grew to
encompass every possible user's most remote needs, the end result
would not be useable by anybody (a Grid component with 27 required
parameters of which six are detailed interfaces, etc., etc.). The
point is, the common components need
