Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.23 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Fri, 12 Jul 2013 10:40:38 -0700
Subject: Re: Converting scripts to node
Thread-Topic: Converting scripts to node
Thread-Index: Ac5/JuyDWmWW5WWOTmuuMKbESwfHvw==
Message-ID: <CE058B55.224E6%fil@adobe.com>
In-Reply-To: 
 <CADVgkyOsuagc4we9A=xPBYMc1nY=4AOxZhXAA-7TsDSAuiDz7w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.5.130515
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I have to agree with Lorin on this one. Windows scripts are getting
ignored and not maintained, no surprise. Moving to node won't eliminate
windows neglect but should mitigate the issue of unix fixes not making
their way into windows scripts. Don't think it's super high priority to
get done soon, though.

On 7/12/13 10:27 AM, "Brian LeRoux" <b@brian.io> wrote:

>So, science experiment. That's cool. [1]
>
>[1] https://twitter.com/jonathanpenn/status/355696329172844549
>
>
>
>On Fri, Jul 12, 2013 at 10:07 AM, Filip Maj <fil@adobe.com> wrote:
>> Main benefit here is abstracting away two scripts for *nix &
>> windows-compatible platforms like android and blackberry. BB already
>>uses
>> node for those anyways..
>>
>> On 7/12/13 9:47 AM, "Brian LeRoux" <b@brian.io> wrote:
>>
>>>Most of the scripts themselves shell out to things like adb or
>>>whatever so putting another layer of scripting abstraction over top
>>>feels unnecessary (to me). I suppose the benefit is that on Android
>>>we'd have less code?
>>>
>>>Are there other benefits?
>>>
>>>
>>>
>>>On Thu, Jul 11, 2013 at 6:55 PM, Andrew Grieve <agrieve@chromium.org>
>>>wrote:
>>>> Cool!
>>>>
>>>> I don't think npm is a good idea for them since that will add another
>>>> avenue for mistakes to be made. Shelling out to them seems fine. You
>>>>can
>>>> also just require() them if you're sure they aren't going to mess up
>>>>you're
>>>> apps state (e.g. change your CWD), but shelling out is certainly
>>>>safer.
>>>>
>>>>
>>>> On Thu, Jul 11, 2013 at 6:24 PM, Filip Maj <fil@adobe.com> wrote:
>>>>
>>>>> Don't think for android specifically there has been any work on this
>>>>>
>>>>> On 7/11/13 2:55 PM, "Andrew Grieve" <agrieve@chromium.org> wrote:
>>>>>
>>>>> >We talked about unifying on node post 3.0 for our scripts (e.g.
>>>>>android
>>>>> >create script).
>>>>> >
>>>>> >Was wondering if anyone had started on this?
>>>>>
>>>>>
>>