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 <[email protected]> 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 [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.
>  
>  

-- 
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.


Reply via email to