Hi,
you can go for arrays and a more flexible approach, but you will spend time building the framework, compare to spend time building the final app. so this is always a difficult choice. Basically, if you think you will have to do this again for another book, or actually several other books, you might then think about building a framework that use arrays, resources and descriptiong of the book in xml or something, and then have a "reader", but as I said, it's much more work than hardcoding things. I always tend to avoid hardcoding things tho... but it sometimes make sense from a production point of view where you can deliver faster if the specs are rock solid ( else, if the client changes a small feature, you are in for a complete rewrite if everything is hardcoded)
bye,
Jean