The site
http://cordova.apache.org/docs/en/edge/cordova_plugins_pluginapis.md.html#Plugin%20APIs
says
Non-English translations of these plugin docs can be found by looking at older
versions of the Cordova documentation. Use the drop-down menu at the very
top-right of this site to switch versi
Interesting. Um, I've got nothing to add here I guess. ;) I am curious to see
what folks out there think.
From: agri...@google.com on behalf of Andrew Grieve
Sent: Monday, February 10, 2014 9:34 PM
To: dev
Subject: Re: Plugins Release!
Feedback definite
Feedback definitely welcome in this department.
For the 3.4.0 release, the main docs for plugins will look like:
http://cordova.apache.org/docs/en/edge/cordova_plugins_pluginapis.md.html#Plugin%20APIs
On Mon, Feb 10, 2014 at 10:07 PM, Ray Camden wrote:
> Is that the plan for 'core' plugins too?
Is that the plan for 'core' plugins too? Won't that make it difficult for
someone to see PG features as a whole? Will there be an index of some sort to
make it easier to browse perhaps?
Sorry for all the questions - just thinking about this from the perspective of
folks *not* on this list.
__
The docs should be in the repo for the plugin itself, under the docs folder:
https://github.com/apache/cordova-plugin-camera/blob/master/doc/index.md
We're moving the docs to the plugin repo itself I believe, to de-duplicate
things.
On Mon, Feb 10, 2014 at 5:14 PM, Ray Camden wrote:
> Dumb que
Dumb question, but when I see things like this in the blog post:
org.apache.cordova.camera
CB-4919 firefox os quirks added and supported platforms list is updated
Where is that actually documented? Since I've seen quirks listed in the main
doc I assumed it would be there, but I do not see it he
Hey James,
Our release process for plugins can be found at
https://wiki.apache.org/cordova/StepsForPluginRelease
org.apache.cordova.* is reserved for apache cordova commiters only.
We can merge as often as once a week to once a month. Just depends on need.
I just completed a dev -> master merge
shipped.
http://cordova.apache.org/news/2014/02/10/plugins-release.html
On Sat, Feb 8, 2014 at 8:43 AM, Andrew Grieve wrote:
> ship it.
>
>
> On Fri, Feb 7, 2014 at 7:35 PM, Steven Gill
> wrote:
>
> > ship it?
> >
> >
> > On Fri, Feb 7, 2014 at 12:03 PM, Steven Gill
> > wrote:
> >
> > > Than
I mostly agree with Braden, except would like to see a top-level CLI
command to do that automatically. `cordova upgrade` could re-add installed
platforms and plugins in a temporary location, and swap it into your
project root only if it completes successfully, and also moving your old
version into
Thanks Shazron, that helps a lot. A few more quick questions:
* How does permissions work with plugman? What would happen if I tried
to publish a org.apache.cordova.* plugin?
* How often do you guys merge dev -> master?
I'm glad to you that you can specific branches and tags, I didn't know that!
Been using this Friday / today and am LOVING IT
So much faster to discover & process PRs.
I've been going through and merging things. I've ignored those on WP,
Tizen, and BB. If someone could look at those, that would be great!
On Sat, Feb 1, 2014 at 12:23 PM, Bas Bosman wrote:
> Hi Ian,
He Axel, thanks for spearheading this. Will have a look shortly.
On Mon, Feb 10, 2014 at 9:07 AM, Axel Nennker wrote:
> Andrew,
>
> any comments to the current implementation?
> https://github.com/apache/cordova-cli/pull/126
>
> Joe commented that the new class in config_parser.js named "icon"
Andrew,
any comments to the current implementation?
https://github.com/apache/cordova-cli/pull/126
Joe commented that the new class in config_parser.js named "icon" should be
named "Icon" but I left it as is because the other classes are lowercase
too.
There was another comment that namespaces in
13 matches
Mail list logo
