+1 for platforms on npm.
-1 for plugins on npm (best way to create a giant mess).
On Mon, Mar 31, 2014 at 4:18 PM, Jonathan Bond-Caron <
jbo...@gdesolutions.com> wrote:
> On Sat Mar 29 03:11 PM, Brian LeRoux wrote:
> > I think its a great idea. The platforms have a standard interface [1]
> for w
On Sat Mar 29 03:11 PM, Brian LeRoux wrote:
> I think its a great idea. The platforms have a standard interface [1] for
> which the
> higher level CLI Node module depends. We could remove our logic for
> versioning/caching and leave that to npm. We distribute via npm already for
> the
> CLI so th
for(var i in thingByType['templates'])
> >cordova.installTemplate(thingByType['templates'][i]);
> >
> > }).catch(e) {
> >
> > // uh oh, revert install changes
> >
> > }
> >
> > Can cordova_lib.fetch() be replac
; > for(var i in thingByType['templates'])
> >cordova.installTemplate(thingByType['templates'][i]);
> >
> > }).catch(e) {
> >
> > // uh oh, revert install changes
> >
> > }
> >
> > Can cordova_lib.fetch()
lates'][i]);
>
> }).catch(e) {
>
> // uh oh, revert install changes
>
> }
>
> Can cordova_lib.fetch() be replaced by npm? It's a big maybe, losing
> support for --searchpath, github fetching, no more support for plugin.xml &
> probably more details
&g
g maybe, losing support
for --searchpath, github fetching, no more support for plugin.xml & probably
more details
> -Original Message-
> From: Anis KADRI [mailto:anis.ka...@gmail.com]
> Sent: March 28, 2014 6:01 AM
> To: dev@cordova.apache.org
> Subject: Re: Consolidatin
I say we should
On Fri, Mar 28, 2014 at 1:47 AM, Brian LeRoux wrote:
> +1
>
>
> On Thu, Mar 27, 2014 at 7:36 PM, Steven Gill
> wrote:
>
> > Interesting points about plugins. IMO It would be a good amount of work
> to
> > move plugins over to npm. Definitely worth it for us to continue
> discus
+1
On Thu, Mar 27, 2014 at 7:36 PM, Steven Gill wrote:
> Interesting points about plugins. IMO It would be a good amount of work to
> move plugins over to npm. Definitely worth it for us to continue discussing
> the feasibility of it.
>
> As for platforms, most people seem to be in agreement ab
Interesting points about plugins. IMO It would be a good amount of work to
move plugins over to npm. Definitely worth it for us to continue discussing
the feasibility of it.
As for platforms, most people seem to be in agreement about moving them
over to npm and setting them as dependencies for the
I agree that npm would not be able to resolved the dependencies.
That's something that cordova would need to resolved. if plugin A 1.0
depends on plugin B version 1.0, and plugin C 1.0 depends on plugin B
version 2.0
Codova Tool will be the one to determined the final flat set of plugins and
their
Agree we don't want to use node_modules, nor the "dependency" field.
I do think we should use it's fetching logic via "npm cache add" though,
and then copy the downloaded plugin from the npm cache dir to the project.
On Tue, Mar 18, 2014 at 2:59 PM, Anis KADRI wrote:
> I don't see how we can r
I don't see how we can rely on npm's dependency system (or npm install) for
Cordova because npm dependencies consist of a tree of isolated
node_modules/ whereas cordova has to share code amongst multiple plugins
(different build system than npm/node). We could use `npm install` for
auto-fetching bu
Jonathan
Today we don't support that scenario with cordova cli, if a plugin
supports multiple platforms you can't block "cordova plugin add" from
installing to all platforms that it supports.
Maybe a new enhancement request?
My intention with having the dependencies info was solely to get the a
On Fri Mar 14 11:36 PM, Carlos Santana wrote:
> I have being thinking on this sort of problem also.
>
> I think using npm to store none node code is perfectly fine use case.
>
> I vote to leverage npm as the building block and then build cordova functions
> on
> top of it.
>
+1 where possible
I have being thinking on this sort of problem also.
I think using npm to store none node code is perfectly fine use case.
I vote to leverage npm as the building block and then build cordova
functions on top of it.
If we need to download something from the web use npm (leverages user's
already co
On Fri, Mar 14, 2014 at 7:13 AM, Braden Shepherdson wrote:
> Cordova platforms don't map into Cordova plugins very well at all.
>
No, they don't indeed. It would be really interesting to `plugin add` a
platform.
>
> For npm modules, we can specify arbitrary sources, but npm has its own
> ideas
Cordova platforms don't map into Cordova plugins very well at all.
For npm modules, we can specify arbitrary sources, but npm has its own
ideas about where things should be installed. Do we actually want the
platforms, or at least their templates, to live in node_modules? I suppose
that's a reason
+1 to handling both the same way and not using git for distribution.
I'm interested in the pros and cons of using the plugin registry vs npm.
On Thu, Mar 13, 2014 at 10:14 PM, Gorkem Ercan wrote:
> Great idea.. I especially don't like the git archive download. It does not
> really allow us to
Great idea.. I especially don't like the git archive download. It does not
really allow us to track some sort of statistics reliably. I think its
replacement should allow collection of download statistics. The plugins
stats from plugman seems OK. I am not sure if npm would allow such stats.
Not t
+1 to Steve's suggestion
On Thu, Mar 13, 2014 at 2:58 PM, Steven Gill wrote:
> Love these suggestions!
>
> I am a little uneasy about storing the platforms on registry.cordova.io.
> Right now that database is just for plugins + views + ui and adding
> platforms will require us to change some of
Love these suggestions!
I am a little uneasy about storing the platforms on registry.cordova.io.
Right now that database is just for plugins + views + ui and adding
platforms will require us to change some of the requests on
plugins.cordova.io. It is easy enough to do, but I think we have better
Thanks Andrew, this is the sane path, big +1
On Thu, Mar 13, 2014 at 2:27 PM, Michael Brooks wrote:
> Great suggestions Andrew!
>
>
> On Thu, Mar 13, 2014 at 9:33 AM, Brian LeRoux wrote:
>
> > I love it / lots of wins in there
> >
> >
> > On Thu, Mar 13, 2014 at 8:25 AM, Andrew Grieve
> > wrot
Great suggestions Andrew!
On Thu, Mar 13, 2014 at 9:33 AM, Brian LeRoux wrote:
> I love it / lots of wins in there
>
>
> On Thu, Mar 13, 2014 at 8:25 AM, Andrew Grieve
> wrote:
>
> > Right now, CLI downloads & caches platforms & plugins using two different
> > mechanisms, with totally independ
I love it / lots of wins in there
On Thu, Mar 13, 2014 at 8:25 AM, Andrew Grieve wrote:
> Right now, CLI downloads & caches platforms & plugins using two different
> mechanisms, with totally independent code paths.
>
> plugman uses the request library, with proxy settings in .plugman/config.
>
This is one of the several things I want to unify in CLI and Plugman, that
collectively argue for turning both the `cordova` and `plugman` packages
into thin wrappers around a common cordova-lib dependency.
I'm also prototyping some related crazy ideas, but it will be some weeks
before I have a ch
Right now, CLI downloads & caches platforms & plugins using two different
mechanisms, with totally independent code paths.
plugman uses the request library, with proxy settings in .plugman/config.
It downloads the tars directly from registry.cordova.io. It does not cache
them.
CLI uses the reques
26 matches
Mail list logo
