BTW: This isn't a JS API change at all.
On Thu, Jan 10, 2013 at 5:18 PM, Joe Bowser <[email protected]> wrote: > Blargh! Making things merge cleanly has reduced readibility: > > https://github.com/infil00p/cordova-android/commit/5ca233779d11177ec2bef97afa2910d383d6d4a2 > > That's the meat of it. I'm sure there's more in here, but I mostly > want to get the state change code working. For CordovaWebView, we're > probably going to figure out some helper methods to allow users to > restore their states, but when you're working on your own Android App > with custom views, I think it's safe to say that your intents and > states are your own responsibility. > > On Thu, Jan 10, 2013 at 4:48 PM, Brian LeRoux <[email protected]> wrote: >> Love the functionality conceptually speaking but where is this code >> exactly so I can have a look Joe? (There's like a 1000 commits on that >> branch and I'm abjectly lazy.) >> >> On Thu, Jan 10, 2013 at 4:40 PM, Filip Maj <[email protected]> wrote: >>> If it works, don't see why not! >>> >>> On 1/10/13 4:29 PM, "Joe Bowser" <[email protected]> wrote: >>> >>>>Hey >>>> >>>>I'm wanting to merge some of the state code that I was working on >>>>before the break in. Are people still cool with this? >>>> >>>>https://github.com/infil00p/cordova-android/tree/CordovaActivity >>>> >>>>Basically, this lets us restore our state if we got the app killed >>>>while we were in Camera. Assuming that the Camera can store the data, >>>>this should get around the Camera issue. It was called >>>>CordovaActivity because I thought we were going to implement the >>>>Activity. This turned out not to be the case. >>>> >>>>Thoughts? >>>> >>>>Joe >>>
