Re: Google Team's Task Backlog: Android

2013-07-29 Thread Joe Bowser
On Mon, Jul 29, 2013 at 7:29 AM, Andrew Grieve wrote: > On Sun, Jul 28, 2013 at 12:32 AM, Joe Bowser wrote: > >> OK, since we're not talking about each individual one in their own >> thread (or at least a thread I can find), let's talk about them here: >> >> On Thu, Jul 25, 2013 at 10:48 AM, Andr

Re: requestAnimationFrame Re: Google Team's Task Backlog: Android

2013-07-29 Thread Michal Mocny
My understand was that: events fire faster than UI paints, and general good design is to coalesce and update UI once on RAF. In this case, the events came from native and were sent across the bridge, which meant the while the app js could do the coalescing, doing it on the native side meant huge p

Re: requestAnimationFrame Re: Google Team's Task Backlog: Android

2013-07-29 Thread Andrew Grieve
I'm not sure the exact details, but it was something Andrew Trice said he did in his PGD talk. I may not have understood correctly. I think the issue might be that our bridge doesn't have any throttling built in. On Mon, Jul 29, 2013 at 12:01 AM, Jesse MacFadyen wrote: > Hopefully the subject ch

Re: Google Team's Task Backlog: Android

2013-07-29 Thread Andrew Grieve
On Sun, Jul 28, 2013 at 12:32 AM, Joe Bowser wrote: > OK, since we're not talking about each individual one in their own > thread (or at least a thread I can find), let's talk about them here: > > On Thu, Jul 25, 2013 at 10:48 AM, Andrew Grieve > wrote: > > > > cordova-android: > > > > - Change

Re: requestAnimationFrame Re: Google Team's Task Backlog: Android

2013-07-28 Thread Jesse MacFadyen
Hopefully the subject change started a new thread. Why would you use reqAnimFrame for exec? Native calls have nothing to do with repaints, so this makes no sense to me... Sent from my iPhone > On Jul 25, 2013, at 10:49 AM, Andrew Grieve wrote: > > We've done some planning around what we'd like

Re: Google Team's Task Backlog: Android

2013-07-28 Thread Simon MacDonald
On Sun, Jul 28, 2013 at 12:32 AM, Joe Bowser wrote: > > > - Move ExifHelpers out of core and into Camera (used only by Camera) > > This may also be used by Capture when we capture an image. I have no > idea why we have two ways of taking a photo. The reason we have two ways to take a picture i

Re: Google Team's Task Backlog: Android

2013-07-27 Thread Joe Bowser
OK, since we're not talking about each individual one in their own thread (or at least a thread I can find), let's talk about them here: On Thu, Jul 25, 2013 at 10:48 AM, Andrew Grieve wrote: > > cordova-android: > > - Change plugins to have distinct package names How does this work with plugin

Re: Google Team's Task Backlog: Android

2013-07-27 Thread Sharif Ahmed
The changes looks pretty basic to me. Lets see what Joe has to say about the deprecation. Also, I would like to add one more to my interest list: Change plugins to have distinct package names On Sat, Jul 27, 2013 at 1:51 AM, Andrew Grieve wrote: > Cool, all of those seem not too bad, but let'

Re: Google Team's Task Backlog: Android

2013-07-26 Thread Andrew Grieve
Cool, all of those seem not too bad, but let's discuss a bit first: On Fri, Jul 26, 2013 at 11:01 AM, Sharif Ahmed wrote: > Andrew - > The following peeked my interest: > - Move JSONUtils out of core (to minimize API surface) (was added by > our intern a while ago) > - Move FileHelpers out of co

Re: Google Team's Task Backlog: Android

2013-07-26 Thread Sharif Ahmed
Andrew - The following peeked my interest: - Move JSONUtils out of core (to minimize API surface) (was added by our intern a while ago) - Move FileHelpers out of core (Most functionality now lives in CordovaResourceApi) - Move ExifHelpers out of core and into Camera (used only by Camera) - Extract

Re: Google Team's Task Backlog: Android

2013-07-26 Thread Andrew Grieve
Sharif - I don't think anything has been spoke for, anything in particular that peeked your interest? There's also a good list of issues on JIRA available for Android: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Andr

Re: Google Team's Task Backlog: Android

2013-07-26 Thread Andrew Grieve
Yep, that was my intention. On Thu, Jul 25, 2013 at 1:56 PM, Joe Bowser wrote: > Can we break these out and talk about a couple of these? I'm certain > that many of these features will be subject to the Deprecation Policy. > > On Thu, Jul 25, 2013 at 10:48 AM, Andrew Grieve > wrote: > > We've

Re: Google Team's Task Backlog: Android

2013-07-25 Thread Sharif Ahmed
@Andrew I want to contribute to the upcoming features/issues you have just given. Please let me know, how can I go forward in doing it. Maybe assign a few to me, I don't know you tell me :) Thanks. On 7/25/13, Andrew Grieve wrote: > We've done some planning around what we'd like to get done over

Re: Google Team's Task Backlog: Android

2013-07-25 Thread Joe Bowser
Can we break these out and talk about a couple of these? I'm certain that many of these features will be subject to the Deprecation Policy. On Thu, Jul 25, 2013 at 10:48 AM, Andrew Grieve wrote: > We've done some planning around what we'd like to get done over the next > quarter, and so I thought

Google Team's Task Backlog: Android

2013-07-25 Thread Andrew Grieve
We've done some planning around what we'd like to get done over the next quarter, and so I thought I'd share. This isn't to say that we'll be going and doing these things without further discussion or proper JIRA issues. It also doesn't mean we will be solely focused on this list, nor that we'll