5,000 display objects----crazy or what? --Responsive design suggestions requested--

 I have prototyped a spreadsheet style display which is working correctly and is grouped onto a scroll view and data is shown as designed.

However I have two main questions/concerns.

  1. I have tried to optimize the construction of the display objects, but I cannot find a way to avoid the rolling ball busy icon-display lock out for 6 seconds in the simulators-before the spreadsheet is displyed. The code has time delay calls to try to force the display as the lines of the spreadsheet are created. Terminal print outs shows that the code finishes its work and then, and only then, the busy screen lockout occurs while the objects are presumably created and then displayed. I am looking for suggestions on how to force/show lines of the  speadsheet as it is being constructed-this may take longer but will look more responsive to the user.

If not this then concurrently a progress bar.

  1. This number of objects will presumably take up a lot of storage (2500 drawn rectangles and 2500 text objects (50x50 spreadsheet cells). I can reduce the memory by user option but only a little. I cannot easily use background images as different cells need different color fills, based on data so I think I have to construct each cell dynamically. How do I measure storage used ?

Thanks for any suggestions