06-13-2012 06:11 PM
What strategies do you employ in a content heavy application to paginate through items/results. Do you just dynacally generate Pages or Containers with ids and toggle opacity?
I kind of like how PixelMags(BlackBerry World co demoing "anytime" magazine reader") constructed their ui.
06-14-2012 02:54 PM
I thought this would trigger more discussion.
This would depend entirely on the application.
Where is the data coming from?
How likely are you to revisit previous pages?
How much memory is the whole set of pages going to take?
How long does it take to generate pages?
How much needs to be cached?
If memory and speed were not an issue, what would the app look like?
Maybe you have a simple navigation pane, and you create a page and push it, then drop the page when done.
Maybe you have something like double-buffering. You have two pages, one on, one off. Create new page. Swap.
Toggling opacity is an interesting idea. One of the samples did this. Check out the traffic light exercise.