Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.185 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Fri, 22 Mar 2013 14:38:19 -0700
Subject: Re: Platform-level command line scripts ;)
Thread-Topic: Platform-level command line scripts ;)
Thread-Index: Ac4nRZRk1gdovng6RHmHEDXftsn0qw==
Message-ID: <CD72165C.1B182%fil@adobe.com>
In-Reply-To: 
 <CADVgkyOs0v2gy+KX2RWrUNELkLZT=4AvD0o9gniwBsoO3HFx2Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hai gaiz!

Main contention between the two "camps" in this debate is four vs eight
scripts.. But Brian points out that refactoring smaller bits of
functionality into their own script allows us to "have our cake and eat it
too". This, in turn, results in four + (a subset of the 8) =3D 10 scripts i=
n
total.. Which is an argument for just starting with smaller more discrete
scripts to begin with, lol.

How about this as a middle ground:

- under /cordova/ we have the four scripts Anis/Andrew recommend: clean,
log, build and run. These call into various scripts under cordova/lib,
such as..
- under /cordova/lib we have the ~6 scripts I recommended: build-debug,
build-release, start-emulator, deploy-device, deploy-emulator, and
possibly a list-devices one as well.

The final point is nailing what `run` does, step-by-step. Paraphrasing
Anis:

If device(s) connected:
* Pick device (ignore emulators).
* Prompt, timeout and pick first one (5 to 10 seconds) if multiple devices
are connected (ignore emulators).

If device(s) not connected:
* Emulator if it is running
* Prompt, timeout and pick first one (5 to 10 seconds) if multiple
emulators are running.
* Start emulator. If you have multiple ones set up (Android's case),
prompt, timeout and launch first one (5 to 10 seconds).

Yes/no/discuss. Let's try to get to a consensus :)


On 3/21/13 5:29 PM, "Brian LeRoux" <b@brian.io> wrote:

>I knew you'd bring that up! We'll talk more tmrw.
>
>On Thu, Mar 21, 2013 at 4:40 PM, Anis KADRI <anis.kadri@gmail.com> wrote:
>> =8Aor you can have functions do discrete actions like so:
>>
>>=20
>>https://git-wip-us.apache.org/repos/asf?p=3Dcordova-android.git;a=3Dblob;=
f=3Dbi
>>n/templates/cordova/cordova;h=3D1945a4c45f835a6eab3836c4154e518b902d88c6;=
hb
>>=3DHEAD
>>
>> =8Ainstead of creating more inodes.
>>
>>
>> On Thu, Mar 21, 2013 at 4:30 PM, Brian LeRoux <b@brian.io> wrote:
>>
>>> > You could make more scripts as helper scripts, but I still think
>>>that it
>>> > will be confusing if a user types "ls" and sees a large number of
>>> scripts,
>>> > having to guess what each of them does.
>>>
>>> Put them in a subdir called ./lib and be done w/ it.
>>>
>>>
>>> > I don't think having more scripts will make it more likely that the
>>> scripts
>>> > will be consistent across platforms.
>>>
>>> Ah, but having smaller responsibilities for a module of code makes it
>>> more testable in discreet form making it easier to confirm said
>>> suspicions.
>>>