I'm about to convert some T4 code to T5. In this code, I have a large ,
paged table of persons with index links with the letters 'a' ..'z' at
the bottom of each page . Clicking the 'c' link starts presenting the
first persons with a name beginning with 'c', There are also links to go
on page forward/backward. Like this:
< a b c d e f g h i j k l m n o p q r s t u v x y z >
This is actually useful, it's much easier to press 'l' looking for
leamas the to try to guess which page nr he is at.
In T4, I had to recode large part of the table stuff , including sort
etc, to implement this. I hoped T5 would be better, but the problem seem
to be still here: The Grid has an internal model of a fixed number of
pages, and a current page nr. This doesn't work with the sliding page
window required to present "the first page of users beginning with x'.
For this to work, the actual page must be defined by the first row nr.
In other words: A flexible Grid should be able to position to any row
in the data, not just to even page boundaries (according to the
default's definition of a page).
So, two questions:
- Am I right thinking that implementing a GridIndex analog to GridPager
isn't straightforward in current design?
- Would i be possible to change the code in Grid to open up for other
paging strategies than a fixed nr of (numbered) pages? In particular,
would it be possible to store currentRow instead of currentPage in Grid?
Cheers,
--alec
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
