OK, have revised your aia, may not be quite what you intend, but possibly something to work on. One complication is that the pager uses a 0 based index (perhaps @vknow360 can fix this at some point), and I combined all your csv files into just one. This means you can work from the main list of lists, instead of having to maintain several lists (of lists). I choose to not handle the Readers, but this can be done by creating complete separate pagelinks files for each reader, or some other method if the pagelinks content would be the same ? I reorganised things so that the "pages" are downloaded when the app starts, but only does this once if the pages already exist in the ASD. Once this is done, you can then just work off the device. I guess the same approach can be used for the sound files, although you may want to just call these as required if large ? The blocks could be further simplified, but I aimed to keep it simple so that you could hopefully follow what I have done, and link back to your original blocks.
Sure, I prefer to download all pages in startup the app as you said. However, I need every csv in seperate because I have just simplify the blocks in order to let me understand how the blocks works. So, is it possible to do that.
You would probably only want three pages, then use logic to load other pages as required. Then you may need to change the way you download pages back to how you were doing, or something similar.
I remember doing something similar some time ago for Osama Sayer, I will see if I can find it.
Won't you end up with @ 60 csv files instead of 20 ?
Here is one approach to the logic needed to load pages as you swipe, using only five components in the pager. This relies on your page names containing their number in the same position. Additional logic would be needed to go to a specific page - beyond the next or previous page numbers. I guess you could setup a download routine to get the next page whilst on the previous page, so that it is already downloaded when one swipes forward. If you need to swipe to the next page from right to left (instead of how I have done it - left to right), you should be able to easily reverse the logic.