2009-06-25 Thiago H. de Paula Figueiredo:
> 2009/6/25 Przemysław Wojnowski :
> > My point is that the current implementation of Grid#setupDataSource()
> > uses getAvailableRows() to calculate exact values for start and end
> > indices. Shouldn't this be responsibility of GridDataSource?
>
> Nice p
2009/6/25 Przemysław Wojnowski :
> My point is that the current implementation of Grid#setupDataSource()
> uses getAvailableRows() to calculate exact values for start and end
> indices. Shouldn't this be responsibility of GridDataSource?
Nice points in the whole message. :)
One solution would be t
Dnia 2009-06-24, śro o godzinie 12:19 -0300, Thiago H. de Paula
Figueiredo pisze:
> > Why Grid#setupDataSource() is calculating endIndex and not allowing for
> > GridDataSource to do it? Why GridDataSource#prepare method have
> > startIndex and endIndex parameters and not offset/limit pair?
>
> As
2009/6/24 Przemysław Wojnowski :
> Hi!
Hi!
> Why Grid#setupDataSource() is calculating endIndex and not allowing for
> GridDataSource to do it? Why GridDataSource#prepare method have
> startIndex and endIndex parameters and not offset/limit pair?
As offset = startIndex and limit = endIndex - sta
Hi!
Why Grid#setupDataSource() is calculating endIndex and not allowing for
GridDataSource to do it? Why GridDataSource#prepare method have
startIndex and endIndex parameters and not offset/limit pair?
I'm asking, because if GridDataSource could calculate endIndex (or use
limit instead) for itself
