Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of agrieve@google.com designates
 209.85.214.175 as permitted sender)
MIME-Version: 1.0
From: Andrew Grieve <agrieve@google.com>
Date: Mon, 15 Oct 2012 20:43:10 -0400
Message-ID: 
 <CABiQX1VRqLi7XHderi5qD8xye=MmnpXV7DgnV+4qexhdVREjSw@mail.gmail.com>
Subject: cordova/debug vs. cordova/emulate
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8fb1f196682ddb04cc227198

--e89a8fb1f196682ddb04cc227198
Content-Type: text/plain; charset=ISO-8859-1

Many questions around what these are supposed to do.

The current state:
iOS:
cordova/debug: Does a clean build in debug mode
cordova/emulate: Does a build if the app does not exist, but doesn't
attempt to build if it's there but stale. Runs the app in the simulator via
ios-sim

Android:
cordova/debug: Builds and installs the app on a running emulator
codrova/emulate: Starts an emulator, but doesn't launch the app. Doesn't
build or install the app.

I'm not sure about other platforms...

There's was a recent proposal (today even?) about changing cordova/emulate
to launch the app in Ripple. That might make sense, although I think Ripple
may make more sense as a separate platform in the CLI world (e.g. "cordova
platform add ripple").

on iOS - why do a clean build instead of a regular build?
on Android - why not build from emulate? Is there a way to launch the app
via adb (probably there is).
on both platforms - "debug" doesn't make sense to me. How about calling it
"build"
on both platforms - I think it would make more sense if "emulate" always
performed an incremental build first.


Thoughts on any of this?

--e89a8fb1f196682ddb04cc227198--