-Original Message-
From: Raymond Camden [mailto:raymondcam...@gmail.com]
Sent: Friday, March 6, 2015 6:09 PM
To: dev@cordova.apache.org
Subject: Re: Some thoughts/questions on the new --save feature
Well to be clear, I thought at first this was a *released* feature, just not
one documented
' is the only user
preference that we might have for now.
Thanks,
Nikhil
-Original Message-
From: Mefire O. [mailto:ommen...@microsoft.com]
Sent: Thursday, March 5, 2015 12:37 PM
To: dev@cordova.apache.org
Subject: RE: Some thoughts/questions on the new --save feature
Yep, I think
-Original Message-
From: Raymond Camden [mailto:raymondcam...@gmail.com]
Sent: Friday, March 6, 2015 6:09 PM
To: dev@cordova.apache.org
Subject: Re: Some thoughts/questions on the new --save feature
Well to be clear, I thought at first this was a *released* feature, just not
one documented
preference that we
might have for now.
Thanks,
Nikhil
-Original Message-
From: Mefire O. [mailto:ommen...@microsoft.com]
Sent: Thursday, March 5, 2015 12:37 PM
To: dev@cordova.apache.org
Subject: RE: Some thoughts/questions on the new --save feature
Yep, I think both options should
On Fri, Mar 6, 2015 at 8:30 PM, Mefire O. ommen...@microsoft.com wrote:
- autosave IS a released feature. The 4.3.0 release includes it.
- I don't think the feature may go away, I think it just feels dirty to
instruct users to directly edit the .cordova/config.json file. It doesn't
seem to
: Thursday, March 5, 2015 12:37 PM
To: dev@cordova.apache.org
Subject: RE: Some thoughts/questions on the new --save feature
Yep, I think both options should be documented.
Thanks,
Mefire
-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
I don't have strong feelings about this.
When designing this, some wanted to have --save be default, some wanted to
match npm for the sake of matching npm. In the end both ways were
implemented.
I don't think we need to spend a lot of time on strategizing this. If some
one wants to doc it, go
Yep, I think both options should be documented.
Thanks,
Mefire
-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve
Sent: Thursday, March 5, 2015 11:28 AM
To: dev
Subject: Re: Some thoughts/questions on the new --save feature
I don't have
Consensus is a strong word ;)
On Thu, Mar 5, 2015 at 11:02 AM, Raymond Camden raymondcam...@gmail.com
wrote:
Hmm. Ok... so... is there a consensus to *not* promote it?
On Thu, Mar 5, 2015 at 9:24 AM, Gorkem Ercan gorkem.er...@gmail.com
wrote:
config.son is not created by CLI by default
Heh, ok, so how about - for the typical Cordova user.
And I'd still like to know where/if the settings for this file are documented?
On Thu, Mar 5, 2015 at 10:24 AM, Michal Mocny mmo...@chromium.org wrote:
Consensus is a strong word ;)
On Thu, Mar 5, 2015 at 11:02 AM, Raymond Camden
I don't think they are documented. There's really no settings in there
(besides this one) that anyone would ever need to use. So this would be the
time to add docs. However, I do think we should try and promote just one
way of doing things before branching pointing out there are hidden knobs.
On
On 5 Mar 2015, at 12:01, Raymond Camden wrote:
just one way of doing things
This confuses me though. It seemed as if this new config (I mean new
to me) was a way to configure the CLI. Is there another way to
configure the CLI? With the example that was given (default to auto
save) being a
So, to me this file is a good way to automate the autosave feature just as
Gorkem is pointing (configure the JSON file, add plugins in the usual way
with cordova plugin add and share your project, no flags needed to simply
allow a good, or best, SCM practice), but it has been mentioned that the
Also also, I'm not sure we should actively promote it. It seems like the
kind of config file we want to phase out.
-Michal
On Thu, Mar 5, 2015 at 10:22 AM, Michal Mocny mmo...@chromium.org wrote:
By default, they do not get created unless they have non-default values.
This is usually only
config.son is not created by CLI by default anymore. You need to do
create the file and add the key.
--
Gorkem
On 5 Mar 2015, at 7:33, Raymond Camden wrote:
Sorry - what file? I don't have that in my project. If you meant user
root, I don't have it there either.
On Tue, Mar 3, 2015 at 12:14
Hmm. Ok... so... is there a consensus to *not* promote it?
On Thu, Mar 5, 2015 at 9:24 AM, Gorkem Ercan gorkem.er...@gmail.com wrote:
config.son is not created by CLI by default anymore. You need to do create
the file and add the key.
--
Gorkem
On 5 Mar 2015, at 7:33, Raymond Camden wrote:
just one way of doing things
This confuses me though. It seemed as if this new config (I mean new
to me) was a way to configure the CLI. Is there another way to
configure the CLI? With the example that was given (default to auto
save) being a preference for the tooling - can we accomplish that
Sorry - what file? I don't have that in my project. If you meant user
root, I don't have it there either.
On Tue, Mar 3, 2015 at 12:14 PM, Gorkem Ercan gorkem.er...@gmail.com wrote:
You can enable auto save by adding auto_save_plugins to be true on the
.cordova/config.json file. I think this
Definitely - once I find the file. ;)
On Tue, Mar 3, 2015 at 12:20 PM, Michal Mocny mmo...@chromium.org wrote:
Worthy of a blogpost, Ray!
On Tue, Mar 3, 2015 at 1:17 PM, Victor Sosa sosah.vic...@gmail.com wrote:
Good to know this trick. .. Thanks, Gorkem!
2015-03-03 12:14 GMT-06:00 Gorkem
I found this doc, https://wiki.apache.org/cordova/ConfigurationFiles,
which mentions that you can have a .cordova/config.json in projects
and your user dir. I don't have them in either location. Does that
mean - by default - they don't exist until I make one?
If so - where is the documentation
1) I would say it is not autosave by default so we follow node/npm style.
You have to be explicit when saving dependencies to node projects. Example
npm install browserify --save.
2) I believe their is a --link command to point to your www for your
Cordova project to use. This isn't a perfect
1) I can see the logic there, but it seems like folks would want to
save so much, overwhelmingly so, that it makes sense to not follow the
expectation here? Also, would our typical user be more familiar with
Node and be confused by this?
2) I know about the link too, my issue is more about what I
Raymond, you should just include your config.xml in the repo along with
your www. It will be imported as part of --copy-from and should (I haven't
tested!) auto-restore plugins with this new feature.
As for default not --save, this is mostly for npm compatibility, but also
because we decided to
Yet more clarification: your git repo should look like:
- www/
- index.html
- ...
- config.xml
- ...
NOT
- config.xml
- index.html
- ...
On Tue, Mar 3, 2015 at 11:59 AM, Michal Mocny mmo...@chromium.org wrote:
Raymond, you should just include your config.xml in the repo along with
your
Also also ;) cca applications include a default .gitignore with these
contents:
---
##
## This file is the suggested default .gitignore to be used by cca
applications
##
# Usually, you shouldn't version control `platforms/` and `plugins/`. They
are
# build artefacts which change from
Thanks Michal. I forgot --copy-from was smart like that. If I remember
right, it can tell if the folder is just WWW crap and use it like
WWW crap, otherwise it merges it into a a new project.
Is that a good way of saying it?
On Tue, Mar 3, 2015 at 11:12 AM, Michal Mocny mmo...@chromium.org
Worthy of a blogpost, Ray!
On Tue, Mar 3, 2015 at 1:17 PM, Victor Sosa sosah.vic...@gmail.com wrote:
Good to know this trick. .. Thanks, Gorkem!
2015-03-03 12:14 GMT-06:00 Gorkem Ercan gorkem.er...@gmail.com:
You can enable auto save by adding auto_save_plugins to be true on the
Good to know this trick. .. Thanks, Gorkem!
2015-03-03 12:14 GMT-06:00 Gorkem Ercan gorkem.er...@gmail.com:
You can enable auto save by adding auto_save_plugins to be true on the
.cordova/config.json file. I think this helps with the case 1
--
Gorkem
On 3 Mar 2015, at 9:27, Raymond
9:00 AM
To: devmailto:dev@cordova.apache.org
Subject: Re: Some thoughts/questions on the new --save feature
Raymond, you should just include your config.xml in the repo along with
your www. It will be imported as part of --copy-from and should (I haven't
tested!) auto-restore plugins
+1
On 4 Mar 2015 5:21 am, Michal Mocny mmo...@chromium.org wrote:
Worthy of a blogpost, Ray!
On Tue, Mar 3, 2015 at 1:17 PM, Victor Sosa sosah.vic...@gmail.com
wrote:
Good to know this trick. .. Thanks, Gorkem!
2015-03-03 12:14 GMT-06:00 Gorkem Ercan gorkem.er...@gmail.com:
You
You can enable auto save by adding auto_save_plugins to be true on the
.cordova/config.json file. I think this helps with the case 1
--
Gorkem
On 3 Mar 2015, at 9:27, Raymond Camden wrote:
1) Is there any reason why --save isn't true by default? It would seem
that in a majority of cases
On Tue, Mar 3, 2015 at 8:10 AM, Raymond Camden raymondcam...@gmail.com
wrote:
1) I can see the logic there, but it seems like folks would want to
save so much, overwhelmingly so, that it makes sense to not follow the
expectation here? Also, would our typical user be more familiar with
Node
We should save the phase 2 planning for a separate thread / next hangout.
Many strong opinions and bikeshedding to be had, lets finish phase 1 and
sit on the changes for a bit to get comfortable.
-Michal
On Tue, Mar 3, 2015 at 1:55 PM, Steven Gill stevengil...@gmail.com wrote:
On Tue, Mar 3,
/cordova-lib/pull/170
Sent from my Windows Phone
From: Michal Mocnymailto:mmo...@chromium.org
Sent: 3/3/2015 9:00 AM
To: devmailto:dev@cordova.apache.org
Subject: Re: Some thoughts/questions on the new --save feature
Raymond, you should just include your
1) Is there any reason why --save isn't true by default? It would seem
that in a majority of cases I'd want to save my plugins to the
configuration file. I definitely see times when I would *not* want to
do so, but it seems like that would be the minority of cases.
2) This is probably an edge
+1 on Raymond's idea, I also why --save isn't default. When talking about
SCMs, the best practice for Cordova applications is to share them with no
platforms nor plugins, so each time a developer checks out the project from
the repo, he/she will need to add the appropriate plugins and desired
36 matches
Mail list logo
