Yes, it is for running application logic and having access to cordova plugins. I only hide the webview because I show only native chrome. Certainly don't go out of your way for me, since right now I don't even use the UIWebView due to memory leak problems, so I have to fork and make cordova changes anyway.
On Mon, Dec 12, 2011 at 7:43 PM, Jesse MacFadyen <[email protected]>wrote: > SideTrack: > To run JavaScript for app logic. Not typical, I have done this too, > although just testing the validity of rendering native components from > js. Becomes something entirely different if you wander too far down > this path. I don't consider this a usecase we HAVE to support. > > Cheers, > Jesse > > Sent from my iPhone5 > > On 2011-12-12, at 3:47 PM, Brian LeRoux <[email protected]> wrote: > > > hold up, I think I need more use cases, and less specifics about 'the > > how' here. I'm at loss to understand why you'd inc a webview only to > > hide it? > > > > > >>> I'm currently working on an app and set of plugins that use native > chrome > >>> on iOS (and eventually Android) exclusively. I don't even show the > webview, > >>> I just have it added as a view somewhere, yet hidden, so it still > works. > >>> > >> > >> Which completely invalidates Brian's assumption: "Plugins do not factor > >> into that > >> use case". >
