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 most
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 wrote:
> Pl
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" wrote:
>On Wed, Nov 7, 2012 at 11:24 AM, Jesse wrote:
>
>> Yeah, I am not excited by emulate/deploy, they are the same thing.
>>
>
>I wouldn't say that. In the
On Wed, Nov 7, 2012 at 11:24 AM, Jesse 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 don't really have a strong
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
On Wed, Nov 7, 2012 at 10:33 AM, Jesse MacFadyen wrote:
> # get a list of devices
> ./bin/emulate -devices
>
> # launch emulator with index of 2
> ./bin/emulate -d:2
>
Sure if you can select the one you want then why not. I like a list better
than auto-selection personally. The reason is that it
# get a list of devices
./bin/emulate -devices
# launch emulator with index of 2
./bin/emulate -d:2
I have never liked our use of the term emulate, as it is for emulators
only where I might want to do the same for a physical device that is
attached. and presumably listed devices could include bot
On Tue, Nov 6, 2012 at 4:58 PM, Jesse 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
> - makes perfect sense to me
>
> When I
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 / --rel
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 wrote:
> +1 no user interaction required.
>
> On 11/6/12 4:5
+1 no user interaction required.
On 11/6/12 4:58 PM, "Jesse" 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
>- makes perfect sense to me
>
>When I did the WP7 tool : (
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
- makes perfect sense to me
When I did the WP7 tool : ( which is used by the script )
CordovaDeploy [ -devices BuildOutputPath -d:Dev
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" 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 display a list of
>runn
Right now when you cordova/emulate and nothing is running, it displays a
list of AVDs to choose from. I believe that we should display a list of
running devices/emulators when there is more than one device/emulator
running. As a user, I'd get mad if you automatically picked up the wrong
device/emul
first device, or add an optional index param
this is what WP7 did, haven't tested it a few versions though ..
On Tue, Nov 6, 2012 at 4:17 PM, Filip Maj wrote:
> If you have more than one device/emulator hooked up these scripts fail
> along the lines of:
>
> [exec] error: more than one device and
If you have more than one device/emulator hooked up these scripts fail
along the lines of:
[exec] error: more than one device and emulator
[exec] - waiting for device -
[exec] error: more than one device and emulator
[exec] - waiting for device -
[exec] error: more than one device and emulator
[ex
16 matches
Mail list logo
