Re: Wondering if iUI is suitable for my objectives.
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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Wondering if iUI is suitable for my objectives.
Wow! Glad I didn't read all this before doing something like this (on a much smaller scale) myself. I might have been scared away. :-D Maybe I don't understand the complexity of your needs, but I've found iUI is really quite easy to work with and Remi and Sean are awesome at helping out. :-) You might want to look at the 'Mashboard' code. Sean put a link in my post about multi-column design. -- 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Wondering if iUI is suitable for my objectives.
well... it means you can generate screens on demand :) PROs: - it's generated client-side so less datas get transfered - the initial DOM is very small - you control everything in one place: javascript. no need to make each changes in JS and in serverside generated layouts. - it's an open door to a full offline capability CONs: - you generate in JS, which comes at a perfomance price on low-end devices (aka $80 android) - initial DOM is empty which is really bad for SEO (not a problem here) - you generate layouts from JS, so a graphic designer can't work on it from a separate empty html file - it requires some good JS skills Using createfragments a JSON webservice, this might all be done quickly :) Remi Le Feb 9, 2013 à 11:17 AM, rickyh rickyshamil...@hotmail.com a écrit : Remi Thank you very much for the reply. That is extremely helpful. Scenario 3 is a possibility because the necessary serverside scripts can be written to respond to the AJAX requests and deliver the data. However, please would you explain in a little more detail what you mean by generating the screens client-side? Regards 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Wondering if iUI is suitable for my objectives.
Ok, so if I understand correctly, this amounts to writing an entire application using JavaScript/ECMAScript for execution inside browsers, rather than using native code such as Objective C/Cocoa. The JavaScript is platform neutral which is an advantage, but the performance hit could be considerable. Probably similar amount of work to writing in native code. Not really suitable for my case as I need to wrap an iOS skin around a huge, serverside framework. I am going to reconsider my rejection of the idea of creating a huge HTML doc with all content in it. It won't be any bigger than a PDF copy of the entire lot anyway! That would satisfy the requirement for offline access. Thank you very much, that's been really helpful. R. -- 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Wondering if iUI is suitable for my objectives.
That's pretty much the idea yes, doing what a native app is doing with native code (Obj C, Java, …) in HTML + Javascript. Same amount of work, but for all platforms at once. If offline access is not such a big issue (is your actual CMS works offline?), then #2 might be a good compromise. I'm really not sure having hundreds hundreds of nodes in the DOM is a good idea anyway… you'd probably better split things into separate html files (added to the manifest) and load/unload them by topic/category. (+ huge files HTML cache won't fit that well due to client-side file-size limitations) I'm afraid my answer might ends to something too-engineering. Remi Le 11 févr. 2013 à 14:02, rickyh rickyshamil...@hotmail.com a écrit : Ok, so if I understand correctly, this amounts to writing an entire application using JavaScript/ECMAScript for execution inside browsers, rather than using native code such as Objective C/Cocoa. The JavaScript is platform neutral which is an advantage, but the performance hit could be considerable. Probably similar amount of work to writing in native code. Not really suitable for my case as I need to wrap an iOS skin around a huge, serverside framework. I am going to reconsider my rejection of the idea of creating a huge HTML doc with all content in it. It won't be any bigger than a PDF copy of the entire lot anyway! That would satisfy the requirement for offline access. Thank you very much, that's been really helpful. R. -- 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Wondering if iUI is suitable for my objectives.
Remi Thank you very much for the reply. That is extremely helpful. Scenario 3 is a possibility because the necessary serverside scripts can be written to respond to the AJAX requests and deliver the data. However, please would you explain in a little more detail what you mean by generating the screens client-side? Regards 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Wondering if iUI is suitable for my objectives.
Hi Richard, I see 3 valid ways: #1. Forget about transitions load each pages like you do today for desktop. If no transitions is a valid scenario for you, forget about iUI and google about responsive web design. This might not work as a standalone app btw. #2. Generate screens and use iUI built-in mechanism to load them in ajax. In this scenario, you have a home screen with a list of links. Rather than have all screens in the DOM on load, each link loads the requested screen, adds it to the DOM and make a transition to it. Look at http://demo.iui-js.org/test/link-types.html demo, and how Ajax link (fragment) loads this file/screen and do the job. #3. Generate screens client-side, and populate them via a homemade web service. Here, you generate screens on-demand, with Ajax call to only returns datas. That's the most deluxe scenario to me since it separates UI datas. Not the easiest to implement though… and some extra Javascript coding might be needed, but is the only way to provide offline capability. All are good solutions. Remi Le 8 févr. 2013 à 14:51, rickyh rickyshamil...@hotmail.com a écrit : Background ~ I am using an open source framework as a content management system (OpenACS + Xowiki). The framework makes virtually no use of AJAX, with most page requests a round trip to the server (with some minor exceptions). I am going to store approximately 1000 pages of reference information, where each page will correspond to a subject. The service will be accessible as a standard website, but I also want to make the service available so that iPad users experience it as what the Apple design docs describe as a 'WebApp'. Need I will need an alphabetical list navigation zone, where users can select a subject and have the content displayed, either in an adjacent zone or as a full page with a standard Apple 'back' button (I can customise the underlying platform to provide a feed for the Apple style 'back' button). What concerns me is that the initial 'getting started' guide for iUI suggests that iUI will attempt to download all 'screens' on page load. This would be a performance disaster because I cannot countenance grabbing the entire database of documents at once (bandwidth/local storage etc.) So, Quesions: 1) Can I use iUI in this more conventional context, with standard http requests when links are selected? 2) If so, if I later add AJAX support to the back-end, could I configure iUI to load only the selected page behind-the-scenes, and then apply the animated page transition that is normally does to better imitate a native application? Regards 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 iphonewebdev+unsubscr...@googlegroups.com. To post to this group, send email to iphonewebdev@googlegroups.com. Visit this group at http://groups.google.com/group/iphonewebdev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
