s useful, I can contribute it. I'd have to change the license, I simply
grabbed the MIT license because it was easy, but that's not a problem.
On 9/14/2014 9:38 PM, Michal Mocny wrote:
A different name might be better, since we may publish a cordova-create
module in the future that litera
..Thats what cca does (install platforms based on host OS), coupled with
which sdks the user has installed, and its worked fine for us. Can take a
look at here:
-
https://github.com/MobileChromeApps/mobile-chrome-apps/blob/master/src/auto-upgrade.js#L31-L41
-
https://github.com/MobileChromeApps/mo
Really cool!
If you have your own project template you could do most of this with the
cordova restore command. I have got a new PR[1] that will allow the
restore/save to support to local directories and git urls.
Platform restore list per host OS is interesting, I should look into that.
[1] https
John --
That's pretty awesome! A different name might be a good idea, but I don't
know what name would be short and to the point while conveying what the
tool really does (Good luck, there!). Still, it looks really cool and I
suspect I'll find myself using it quite a bit... :-)
_
A different name might be better, since we may publish a cordova-create
module in the future that literally just creates an empty shell (aka what
`cordova create` does).
I think this is more like a boilerplate app (akin to what yeoman does,
perhaps). No suggestions beyond that.
Anyway, thanks
I recently created a node module called Cordova-create that takes care of the
typical developer new project workflow.
It makes calls to create, then adds a set of platforms and a set of plugins to
the project. I did this because I found myself performing the same steps over
and over again and