I'd rather we saved this for a future refactoring. Bigger fish to fry.
On Wed, Apr 10, 2013 at 12:22 PM, Anis KADRI <[email protected]> wrote: > I feel like I am going to be alone on this one again but as far as I am > concerned I don't like the idea of introducing a dependency. > I think too much importance is given to these scripts. Get them working and > on par with other platforms and then forget about them. The SDK tools > rarely change and so should these scripts. > > Also, if you want to introduce node as a dependency you might as well do it > across the board (that is bin/ scripts included). Once your project is > generated you will need node to build/run/clean/log etc...so what's the > point ? > > > On Wed, Apr 10, 2013 at 11:19 AM, Benn Mapes <[email protected]> wrote: > > > For the new cli scripts (build/run/clean/log & lib/*) I propose that we > > introduce a Node dependency so that there is only one set of code that > > needs to be maintained for these (instead of using bash & jscript). This > > would only mean that people not using the cli (or don't have node > > installed) won't be able to run these commands to test their project. > > > > For the bin scripts we should leave as is so that people without Node can > > still create a project and then use eclipse like most android developers. > > > > ~Benn > > >
