I'm NOT a physicist!


But may be i have a couple of ideas.
Even if the grid has not been developed for such a huge amount of data
something can be done.
The grid loads the data in a memory structure (an array for now)
and the "paints" the grid creating rows=layouts and columns=textviews.
First idea
Every time a row is added the array must be resized.
But data could also be added in some sort of bulk mode.
Thus allowing to dimension the array only one time.
Second one
The grid uses a memory structure to store and views to display
(i've designed it in this way to allow in-place editing in the future).
But adding a flag i could use the textviews to store the data too.
Third one
Not mine (yust an improvement of mahares one)
The grid could load all the data in the memory structure and
show "a page" of them.
First, second third or a mix?
May be none!
Sure to make the choice a need at least 2 data.
1) Load time of the data form the database into the memory table.
2) Creation time of the 250000 textviews
I'd also like to know the maximum time mahares can wait.
Waiting for the database (if possible).
If not ...
It's ok anyway.
Be patient!
My response times are slow!
