Yes, after a bit more work on thinking this through, and a clearer idea now of the interface requirements, option 2 is clearly the way to go.
Initially I will work on the online version. I need the two column layout ( as per this document: http://code.google.com/p/iui/wiki/iuiPad ), with navigation (alphabetical list) in LH column, and will load each page as a full page request initially for the prototype. Once that is working I will write the serverside code to support loading the content asynchronously. For the offline version I will deliver the whole document in one HTML page and try it out. If too big, I'll find a way to split it up. So now I am super interested in the state of the two column code. I had already done a lot of the iOS styling of my serverside framework in raw css for this without using iUI, but now I understand it better I see the folly of continuing down that road. I have therefore decided to begin again using iUI. However the two column layout will be a critical component! Please would you let me know the current state of play with this (http://code.google.com/p/iui/wiki/iuiPad), if I could feasibly use it now for a prototype, and what the future holds. Many thanks, Richard -- You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
