Ah, yes, you're right. Start index should be 10 in my example. Its okay
then.
On Mon, Dec 17, 2012 at 12:58 PM, Muhammad Gelbana wrote:
> Isn't the starting index always dividable by rowsPerPage ?
> I logged whats happening on my machine:
>
> prepare(): StartIndex: 0 EndIndex: 4 (I always add 1 t
Isn't the starting index always dividable by rowsPerPage ?
I logged whats happening on my machine:
prepare(): StartIndex: 0 EndIndex: 4 (I always add 1 to the endIndex
because I'm using JDO and it's range is exclusive at the higher limit)
getRowValue(): Index: 0 StartIndex: 0 RowsPerPage: 5 Index-
No, they're not the same:
index 9 startIndex 9 rowsPerPage 5 index-startIndex 0
index%rowsPerPage 4
On Mon, Dec 17, 2012 at 4:17 AM, Muhammad Gelbana wrote:
> I did, they are the same. Although modulating tolerates a glitch I'm trying
> to understand why is it happening. I have 20 rows per p
I did, they are the same. Although modulating tolerates a glitch I'm trying
to understand why is it happening. I have 20 rows per page. The thing is
that, sometimes, the passed index to the getRowValue method is like 0,
while the startindex is 20 !
On Mon, Dec 17, 2012 at 12:00 AM, Geoff Callender
On 17/12/2012, at 3:10 AM, Muhammad Gelbana wrote:
> Marvelous ! You deserve a medal or something :D
> Although I know "jumpstart" is a very resourceful project for tapestry
> beginners including me, I don't why I keep forgetting about it ! May be I
> should have it as my homepage instead of googl
Marvelous ! You deserve a medal or something :D
Although I know "jumpstart" is a very resourceful project for tapestry
beginners including me, I don't why I keep forgetting about it ! May be I
should have it as my homepage instead of google ehehe
About the getRowValue(int) method:
preparedResults
Newly added: a working example using GridDataSource here:
http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/griddatasources
Cheers,
Geoff
On 15/12/2012, at 2:46 AM, Lance Java wrote:
> Basically, the prepare() method is used to fetch the rows between startIndex
> and
That's exactly what I was facing. Thank you for your time :)
On Fri, Dec 14, 2012 at 5:46 PM, Lance Java wrote:
> Basically, the prepare() method is used to fetch the rows between
> startIndex
> and endIndex in a single batch and cache them. This cache might be a list
> with indexes ranging from
Basically, the prepare() method is used to fetch the rows between startIndex
and endIndex in a single batch and cache them. This cache might be a list
with indexes ranging from 0 to (endIndex - startIndex)
getRowValue(int index) is then used to retrieve a single entry from the
batch. This might re
JDBC supports paging which is is available in both hibernate and JPA.
Tapestry provides GridDataSource implementations for both Hibernate and JPA
that support paging.
http://tapestry.apache.org/tapestry5/apidocs/src-html/org/apache/tapestry5/hibernate/HibernateGridDataSource.html
http://tapestry.a
The thing is that my list isn't loaded once. It's loaded on every prepare
as I retrieve it from the database. And the available rows count changes on
every call as more items are available in the database. I solved this be
modulating the provided index, in the getRowValue(int) method, by the
availa
Take a look at the CollectionGridDataSource source code for inspiration:
http://tapestry.apache.org/tapestry5/apidocs/src-html/org/apache/tapestry5/internal/grid/CollectionGridDataSource.html
If you pass a collection to the Grid, tapestry will coerce it to a
CollectionGridDataSource
--
View thi
As far as I can tell, the provided row index is based on the page and not
the currently displayed list of items. Meaning if I have 3 pages and each
page is displaying 5 elements, on the second page, the first element's
index is 5 rather than 0.
But when *prepare()* is called, the start index and e
13 matches
Mail list logo
