Max, should I redirect all InAppBrowser issues to you if you're already on it?
Here's some thoughts: * I think that it needs to be broken out into multiple classes. The InAppWebView is becoming non-trivial, and probably should have its own class. * I can tweak the UI so that it's a bit better. I don't like the black background, and it should have a refresh button, not just a done button. That being said, we should encourage people to just use the browser intent on Android as much as possible. I know that on iOS that InAppBrowser makes sense, but there's a lot of cases where it really just should open Chrome and viewing it in our own thing just looks weird. On Tue, Sep 17, 2013 at 1:38 PM, Michal Mocny <[email protected]> wrote: > +Max who has been finding some issues with what we have and trying to fix > them one by one. I'de love to see some UI sprucing, and I can't speak > specifically to the drawables. > > You suggest that we use accounts on the device as a plugin, well our team > has done just that with the chrome.identity plugin which is available for > vanilla cordova apps: > https://github.com/MobileChromeApps/chrome-cordova/tree/master/plugins/chrome.identity > > That plugin specifically is getting a lot effort put into it from Max right > now, so if there are any limitations just bring them up. > > -Michal > > > On Tue, Sep 17, 2013 at 1:27 PM, Joe Bowser <[email protected]> wrote: > >> Hey >> >> It's come to my attention that InAppBrowser is terrible >> >> 1. We keep getting UI Thread errors >> 2. The UI is awful (on Android) >> 3. We can now move drawables in plugins >> >> So, I propose that we do a re-write of InAppBrowser and add the >> ability to move drawable resources to plugman. Even though I think >> that InAppBrowser sucks and that we should have plugins to use >> different accounts on the device instead of Web OAuth, we're stuck >> with this until someone gets around to actually doing it. >> >> So, Are people cool with this plugin getting re-worked? >> >> Joe >>
