Re: Cordova CLI (and by proxy, platform) requirements

2013-01-29 Thread Filip Maj
Thanks for the feedback everyone! Very helpful. Sounds like we will keep the prompting around. I will add (an issue for) CLI parameters to allow providing any required information to enable automation. Final question, for the platforms that require more configuration: should we prompt on every pl

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-29 Thread Giorgio Natili
Is it possible to do both? I mean path/configuration and if the path/configuration is not found a prompt. Giorgio On 1/29/13 6:13 PM, "Michael Brooks" wrote: >About a year and a half ago, I started to refactor the BlackBerry bin/ >(ANT) script. My goal was the following: > >1. Use SDK path if e

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-29 Thread Michael Brooks
About a year and a half ago, I started to refactor the BlackBerry bin/ (ANT) script. My goal was the following: 1. Use SDK path if explicitly stated in the config file (project.properties) 2. Otherwise search the PATH and use the SDK found 3. Otherwise fail noisily Back during our client work day

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Filip Maj
Totally agree Jesse. My first pass at BB support includes interactive prompting. I would love to get rid of it, or provide another way to specify that stuff. Like you say, perhaps command line options is the way to go (if someone wants to automate the use of the script, for example). The easy fix

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Don Coleman
The current BlackBerry interactive script works well, except I need to look up and copy the path every time. Without cordova cli I copy project.properties from an old BlackBerry project into the new project and edit as necessary. I don't think requiring BlackBerry on the path will work. For supp

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Jesse
Fil, It will most likely not just be BB, so your solution may not be future proof. I would draw a line in the sand stating that there must be a bb-config file which instructs the cli build command of which sdk version to use (via an explicit path ). OR it could be a command line argument at build t

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Filip Maj
So that's what I'm trying to see if we can fix. The multiple SDKs that use the same executable script name throws a wrench into this whole thing.. Lame. What if we drew a line in the sand and said for BlackBerry we only support BB10? Then we can get rid of prompts and tell people to put their BB1

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Brian LeRoux
uh oh. so, does this mean we do both and put prompting behind a configuration option? RECURSIVE ERROR On Mon, Jan 28, 2013 at 5:25 PM, Gord Tanner wrote: > I think the reason blackberry doesn't put the sdk on the path is because they > need to have multiple sdk versions (all with the same comma

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Andrew Grieve
I think there are good reasons for either approach. How about we default to an SDK path that's listed in your config file, and if none exists, use what's on your PATH. On Mon, Jan 28, 2013 at 6:25 PM, Gord Tanner wrote: > I think the reason blackberry doesn't put the sdk on the path is because

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Gord Tanner
I think the reason blackberry doesn't put the sdk on the path is because they need to have multiple sdk versions (all with the same command names) on the same machine. -1 for path +1 for prompting Sent from my iPhone On 2013-01-28, at 6:22 PM, Jesse MacFadyen wrote: > +1 path and configurati

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Jesse MacFadyen
+1 path and configuration for credentials. -1 prompting for values, or confirming previous values. I think the tool should be non-interactive, or at least that is my expectation. On fail simply provide advice on how to remedy the situation. Prompting for a path is out of scope IMO. Its much bett

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Don Coleman
I have the Android tools in my path but not BlackBerry. Prompting for the BlackBerry file locations and passwords etc works OK. It would be nice to search the default location, or at least store all this info in ~/.cordova-cli so the next time I run the tool I can just confirm the previous entries

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Simon MacDonald
+1 PATH Simon Mac Donald http://hi.im/simonmacdonald On Mon, Jan 28, 2013 at 5:14 PM, Filip Maj wrote: > Hey all, > > Working out some bootstrap-type stuff for cordova-cli. Here's a situation > I am dealing with now in the cli code that I would like people's input. > > When you add Android to yo

Re: Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Anis KADRI
+1 PATH variable, config file (in this order). -1 for asking every time. On Mon, Jan 28, 2013 at 2:14 PM, Filip Maj wrote: > Hey all, > > Working out some bootstrap-type stuff for cordova-cli. Here's a situation > I am dealing with now in the cli code that I would like people's input. > > When

Cordova CLI (and by proxy, platform) requirements

2013-01-28 Thread Filip Maj
Hey all, Working out some bootstrap-type stuff for cordova-cli. Here's a situation I am dealing with now in the cli code that I would like people's input. When you add Android to your project's platforms, the requirements, as imposed by the underlying cordova-android library, is that the Android