Re: [Android] ./bin/emulate + debug script behavior

2012-11-08 Thread Brian LeRoux
I really like the API you're proposing Andrew but hesitant to be super bullish on it since I think we are now in CLI API revision 5 or 6. (lulz, software dev) Not attached to the current API but I think this is big enough that requires buy in from Fil, Anis, Jesse, and Mike whom have done the

Re: [Android] ./bin/emulate + debug script behavior

2012-11-07 Thread Brian LeRoux
So the consensus is: ./bin/emulate defaults to first 'thing' and take an optional param for an index if there is more than one Seems to beg we have a script to list emulators/devices now. =/ On Tue, Nov 6, 2012 at 5:00 PM, Filip Maj f...@adobe.com wrote: +1 no user interaction required. On

Re: [Android] ./bin/emulate + debug script behavior

2012-11-07 Thread Andrew Grieve
Here's a proposal for getting rid of our existing scripts, and starting with some new ones (CB-1668): - build --clean == clean first --debug == build in DEBUG mode (default) --release == build in RELEASE mode - run --nobuild == don't run the build command first --debug /

Re: [Android] ./bin/emulate + debug script behavior

2012-11-07 Thread Anis KADRI
On Tue, Nov 6, 2012 at 4:58 PM, Jesse purplecabb...@gmail.com wrote: User interaction should NOT be required, if it annoys you then type the right thing. What would the right thing be ? adb devices - returns a list of usable devices, why not mimic that? adb -s serialNumber command -

Re: [Android] ./bin/emulate + debug script behavior

2012-11-07 Thread Jesse
Yeah, I am not excited by emulate/deploy, they are the same thing. In my mind, the power of CL tooling is as much for programs/scripts as users, interactive steps screw that completely. Maybe the lack of -d: should signal that interaction is required, and the same/similar can be done for the avd

Re: [Android] ./bin/emulate + debug script behavior

2012-11-07 Thread Anis KADRI
On Wed, Nov 7, 2012 at 11:24 AM, Jesse purplecabb...@gmail.com wrote: Yeah, I am not excited by emulate/deploy, they are the same thing. I wouldn't say that. In the case of emulate we could just list emulators and for `deploy` just devices. Or we can have only one command and list both. I

Re: [Android] ./bin/emulate + debug script behavior

2012-11-07 Thread Filip Maj
Please please please let's all agree that no interactive input should be required for the CLI scripts On 11/7/12 11:47 AM, Anis KADRI anis.ka...@gmail.com wrote: On Wed, Nov 7, 2012 at 11:24 AM, Jesse purplecabb...@gmail.com wrote: Yeah, I am not excited by emulate/deploy, they are the same

Re: [Android] ./bin/emulate + debug script behavior

2012-11-07 Thread Andrew Grieve
I don't like the word deploy since that might imply uploading to app-store kind of things. Any beef with my build / run / package proposal? +1 to no user interaction by default. Maybe have an --interactive flag to enable it if we want it. On Wed, Nov 7, 2012 at 3:10 PM, Filip Maj f...@adobe.com

Re: [Android] ./bin/emulate + debug script behavior

2012-11-06 Thread Filip Maj
Yep we should do that. Also think we should have a separate one ( build ? ) that would just compile :) On 11/6/12 4:46 PM, Anis KADRI anis.ka...@gmail.com wrote: Right now when you cordova/emulate and nothing is running, it displays a list of AVDs to choose from. I believe that we should

Re: [Android] ./bin/emulate + debug script behavior

2012-11-06 Thread Filip Maj
+1 no user interaction required. On 11/6/12 4:58 PM, Jesse purplecabb...@gmail.com wrote: User interaction should NOT be required, if it annoys you then type the right thing. adb devices - returns a list of usable devices, why not mimic that? adb -s serialNumber command - makes perfect sense to