+1 for Android/BB would be majorly helpful on those platforms
On Wed, Aug 7, 2013 at 9:15 AM, Filip Maj <[email protected]> wrote: > I agree with you, Andrew. > > Bryan, judging by this thread, it doesn't look like we'll be switching > over to node.js for all platforms, just for android/bb. > > On 8/7/13 7:38 AM, "Andrew Grieve" <[email protected]> wrote: > > >I should also add that when I installed node on windows XP, it had no > >other > >dependencies and was far easier to install than android's other > >dependencies (android sdk, eclipse, JDK). > > > >However, I did also find that at least one of node's apis (getline) didn't > >work on windows. We'll have to still test on all platforms for most > >changes. > > > >I think it'd also be a good idea to either not use any npm dependencies, > >or > >to commit the node_modules directory if we do. That way our users don't > >need to worry about running "npm install" > > > > > >On Wed, Aug 7, 2013 at 10:36 AM, Andrew Grieve <[email protected]> > >wrote: > > > >> +1 for Android. > >> > >> > >> On Wed, Aug 7, 2013 at 10:00 AM, Bryan Higgins > >><[email protected]>wrote: > >> > >>> All BB scripts are already written in node, except for check_reqs. It's > >>> hard to check for the existence of node using node. :) > >>> > >>> If other platforms go that way, we should standardize the location of > >>>the > >>> scripts. I'd like to see them directly invoked by CLI rather than going > >>> through the shell. > >>> > >>> > >>> On Tue, Aug 6, 2013 at 7:24 PM, Anis KADRI <[email protected]> > >>>wrote: > >>> > >>> > +1 if we can somehow automate a user-level node installation (or > >>> > package it somehow). > >>> > > >>> > On Tue, Aug 6, 2013 at 3:28 PM, Filip Maj <[email protected]> wrote: > >>> > > That's a fair answer! I concur. The main win for me is in android > >>>+ BB > >>> > > land, for the reason you name, Jesse. > >>> > > > >>> > > On 8/6/13 3:24 PM, "Jesse" <[email protected]> wrote: > >>> > > > >>> > >>I only think this should be done for the multi-OS platforms. > >>> > >>Elsewhere it is just a make work project IMHO. > >>> > >>I have spent a lot of time ensuring that I was not introducing > >>> > >>dependencies, then we add node, and we get 600 deps. > >>> > >> > >>> > >>@purplecabbage > >>> > >>risingj.com > >>> > >> > >>> > >> > >>> > >>On Tue, Aug 6, 2013 at 3:14 PM, Filip Maj <[email protected]> wrote: > >>> > >> > >>> > >>> I would like to introduce node.js as a dependency for the > >>>platform > >>> > >>> libraries, so that the platform scripts (bin/create, cordova/run, > >>> etc) > >>> > >>>are > >>> > >>> written in node. > >>> > >>> > >>> > >>> Pros: > >>> > >>> - For multi-OS platforms (Android, BlackBerry), this reduces > >>> committer > >>> > >>> cognitive load as the scripts do not need to be authored in two > >>> > >>>different > >>> > >>> script languages (I.e. Shell for unix-y Oses, Wscript for > >>>Windows) > >>> > >>> - consistency in tool/script language. Cordova-js, coho, cli and > >>> > plugman > >>> > >>> are all written on top of node.js. > >>> > >>> > >>> > >>> Cons: > >>> > >>> - Introducing a new dependency > >>> > >>> > >>> > >>> NB: This is separate from platform-spec; I would like to see > >>> > >>>platform-spec > >>> > >>> created/used regardless of the outcome of this thread. > >>> > >>> > >>> > >>> > >>> > > > >>> > > >>> > >> > >> > >
