Thanks to all of you for your thoughts. I went ahead and got my web app running in PhoneGap. For the record, here's what I found.,,
My app worked without change! The only piece I had to put into the PhoneGap project was a simple home page with a link to the existing web app. I put a "Sign In" link on the home page. It requests the SignIn page from the server. Up it came. Magic! So PhoneGap really does act as a glorified browser. I didn't have to re-code my app to be a single web page, and I didn't have to re-architect it into JavaScript client-side making REST calls to the server. It worked without change. However, that leads to the question that Magnus posed in this thread, of whether Apple will look kindly on an app whose behaviour can change after it has been approved...? I'll pick that up in a reply to his post. On 21/01/2014, at 11:50 PM, Geoff Callender wrote: > I've previously written a jQueryMobile app served up by Tapestry and found > that I had to approach it by writing TML files that were pretty much just a > handful of divs as placeholders for JavaScript to fill in. Tapestry handled > all the events (AJAX requests) and returned JSON objects full of data for > JavaScript to turn into HTML and append to the divs. > > I didn't get around to trying to handle input but I'd guess t wouldn't be > very pleasant. > > Can anyone tell me whether their PhoneGap experience was similar, or is it > possible to make more use of Tapestry rendering? Even better, can it make use > of Tapestry form handling? Is there, perhaps, a way with PhoneGap to make use > of the full, glorious, Tapestry AJAX experience? > > Cheers, > > Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
