You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Staci Cooper <st...@gmail.com> on 2015/04/08 20:05:15 UTC
Re: proposed utility
Did anything ever come of this?
I'd be happy to do some work on this if the consensus is that the
implementation needs to be changed.
On Tue, Jan 13, 2015 at 2:10 PM, Staci Cooper <st...@gmail.com> wrote:
> When I was implementing this I initially did add it as a '--local / -l'
> option to the cli. My concern was that it requires the developer to have a
> global installation of Cordova even if all they want is the local command.
> And assuming the user's global and local installs have different version
> numbers, all they would have to do is accidentally omit the -l and they
> would unwittingly use the wrong version of Cordova.
>
> I could add it back in as a flag, or have separate 'cordova' and
> 'cordova-local' commands in
> the cli. Or were you suggesting changing the default behavior of the
> cordova command to shell
> out to local? In which case we could have a flag to turn that behavior off
> for backwards
> compatibility... or to fallback to the global version if no local version
> is found. Hm, I'm not sure..
>
> On Fri, Jan 9, 2015 at 4:35 PM, Jesse <pu...@gmail.com> wrote:
>
>> Do we need to start a discussion around cordova-cli plugins?
>>
>> Personally I prefer keeping this in a separate repo.
>>
>> @purplecabbage
>> risingj.com
>>
>> On Fri, Jan 9, 2015 at 1:08 PM, Tommy Williams <to...@devgeeks.org>
>> wrote:
>>
>> > Just as an aside, I have resorted to:
>> >
>> > alias cdv="./node_modules/.bin/cordova"
>> >
>> > Heh.
>> > On 10/01/2015 8:06 am, "Tommy Williams" <to...@devgeeks.org> wrote:
>> >
>> > > +1 for what Michal describes. Better going forward as well as
>> backwards
>> > > compatibility.
>> > >
>> > > Win win?
>> > > On 10/01/2015 7:54 am, "Michal Mocny" <mm...@chromium.org> wrote:
>> > >
>> > >> I like the way gulp works: the same package acts different when
>> > installed
>> > >> globally/locally. Namely, the global always shells work off to the
>> > local.
>> > >>
>> > >> So, instead of a separate cordova-local utility (akin to grunt and
>> > >> grunt-cli), perhaps we just add your feature directly into
>> cordova-cli?
>> > >>
>> > >> For backwards compat, I think we should still allow the global
>> > cordova-cli
>> > >> to do work as we do now (i.e. we don't *require* local installs), but
>> > if a
>> > >> local install happens to exist it would shell out to that.
>> > >>
>> > >> Anyway, neat that you've implemented this already!
>> > >>
>> > >> On Fri, Jan 9, 2015 at 3:41 PM, Staci Cooper <st...@gmail.com>
>> > wrote:
>> > >>
>> > >> > A while ago I made a utility called cordova-local for managing
>> > multiple
>> > >> > local Cordova installations. It's similar to how grunt/grunt-cli
>> > works;
>> > >> > once installed globally, you run 'cordova-local' instead of
>> 'cordova'
>> > >> and
>> > >> > it will locate and pass its arguments off to the closest
>> installation.
>> > >> >
>> > >> > It's kept and installed independently of the cli but my initial
>> idea
>> > >> was to
>> > >> > keep it in the cordova-cli repo. Since that would complicate the
>> > >> > tools-release/versioning process I closed that PR and would like to
>> > >> propose
>> > >> > including it as a new repo. I added some specs and docs and put it
>> in
>> > a
>> > >> > utilities repo that could be used for similar cli-independent
>> tools,
>> > >> > currently here: https://github.com/stacic/cordova-utility. I added
>> > some
>> > >> > tests to it and also made PRs for documenting the utility in
>> > >> cordova-docs
>> > >> > <https://github.com/apache/cordova-docs/pull/259> and adding it to
>> > the
>> > >> > tools release in cordova-coho
>> > >> > <https://github.com/apache/cordova-coho/pull/61>.
>> > >> >
>> > >> > Opinions? Concerns?
>> > >> >
>> > >>
>> > >
>> >
>>
>
>
Re: proposed utility
Posted by Andrew Grieve <ag...@chromium.org>.
I think my reservation about this tool is that I'm afraid that adding yet
another command to the mix of options will add more confusion than it's
worth.
Those that know the difference between npm local vs. global can trivially
create an "npm run" command (or batch script, or alias, or gulp task) that
calls into node_modules/.bin/cordova.
I think that the clearest guidance we can give is to focus on promoting
just two workflows:
1. Use CLI globally
2. Use cordova-lib locally and call it with gulp/grunt
That said, feel free to post cordova-local to npm :). It's obvious that
some will find it useful.
On Wed, Apr 8, 2015 at 3:42 PM, Parashuram N (MS OPEN TECH) <
panarasi@microsoft.com> wrote:
> Looks like a good candidate to discuss at the monthly hangouts ?
>
> -----Original Message-----
> From: Staci Cooper [mailto:staci.mcl@gmail.com]
> Sent: Wednesday, April 8, 2015 11:05 AM
> To: dev@cordova.apache.org
> Subject: Re: proposed utility
>
> Did anything ever come of this?
>
> I'd be happy to do some work on this if the consensus is that the
> implementation needs to be changed.
>
> On Tue, Jan 13, 2015 at 2:10 PM, Staci Cooper <st...@gmail.com> wrote:
>
> > When I was implementing this I initially did add it as a '--local / -l'
> > option to the cli. My concern was that it requires the developer to
> > have a global installation of Cordova even if all they want is the local
> command.
> > And assuming the user's global and local installs have different
> > version numbers, all they would have to do is accidentally omit the -l
> > and they would unwittingly use the wrong version of Cordova.
> >
> > I could add it back in as a flag, or have separate 'cordova' and
> > 'cordova-local' commands in the cli. Or were you suggesting changing
> > the default behavior of the cordova command to shell out to local? In
> > which case we could have a flag to turn that behavior off for
> > backwards compatibility... or to fallback to the global version if no
> > local version is found. Hm, I'm not sure..
> >
> > On Fri, Jan 9, 2015 at 4:35 PM, Jesse <pu...@gmail.com> wrote:
> >
> >> Do we need to start a discussion around cordova-cli plugins?
> >>
> >> Personally I prefer keeping this in a separate repo.
> >>
> >> @purplecabbage
> >> risingj.com
> >>
> >> On Fri, Jan 9, 2015 at 1:08 PM, Tommy Williams <to...@devgeeks.org>
> >> wrote:
> >>
> >> > Just as an aside, I have resorted to:
> >> >
> >> > alias cdv="./node_modules/.bin/cordova"
> >> >
> >> > Heh.
> >> > On 10/01/2015 8:06 am, "Tommy Williams" <to...@devgeeks.org> wrote:
> >> >
> >> > > +1 for what Michal describes. Better going forward as well as
> >> backwards
> >> > > compatibility.
> >> > >
> >> > > Win win?
> >> > > On 10/01/2015 7:54 am, "Michal Mocny" <mm...@chromium.org> wrote:
> >> > >
> >> > >> I like the way gulp works: the same package acts different when
> >> > installed
> >> > >> globally/locally. Namely, the global always shells work off to
> >> > >> the
> >> > local.
> >> > >>
> >> > >> So, instead of a separate cordova-local utility (akin to grunt
> >> > >> and grunt-cli), perhaps we just add your feature directly into
> >> cordova-cli?
> >> > >>
> >> > >> For backwards compat, I think we should still allow the global
> >> > cordova-cli
> >> > >> to do work as we do now (i.e. we don't *require* local
> >> > >> installs), but
> >> > if a
> >> > >> local install happens to exist it would shell out to that.
> >> > >>
> >> > >> Anyway, neat that you've implemented this already!
> >> > >>
> >> > >> On Fri, Jan 9, 2015 at 3:41 PM, Staci Cooper
> >> > >> <st...@gmail.com>
> >> > wrote:
> >> > >>
> >> > >> > A while ago I made a utility called cordova-local for managing
> >> > multiple
> >> > >> > local Cordova installations. It's similar to how
> >> > >> > grunt/grunt-cli
> >> > works;
> >> > >> > once installed globally, you run 'cordova-local' instead of
> >> 'cordova'
> >> > >> and
> >> > >> > it will locate and pass its arguments off to the closest
> >> installation.
> >> > >> >
> >> > >> > It's kept and installed independently of the cli but my
> >> > >> > initial
> >> idea
> >> > >> was to
> >> > >> > keep it in the cordova-cli repo. Since that would complicate
> >> > >> > the tools-release/versioning process I closed that PR and
> >> > >> > would like to
> >> > >> propose
> >> > >> > including it as a new repo. I added some specs and docs and
> >> > >> > put it
> >> in
> >> > a
> >> > >> > utilities repo that could be used for similar cli-independent
> >> tools,
> >> > >> > currently here: https://github.com/stacic/cordova-utility. I
> >> > >> > added
> >> > some
> >> > >> > tests to it and also made PRs for documenting the utility in
> >> > >> cordova-docs
> >> > >> > <https://github.com/apache/cordova-docs/pull/259> and adding
> >> > >> > it to
> >> > the
> >> > >> > tools release in cordova-coho
> >> > >> > <https://github.com/apache/cordova-coho/pull/61>.
> >> > >> >
> >> > >> > Opinions? Concerns?
> >> > >> >
> >> > >>
> >> > >
> >> >
> >>
> >
> >
>
RE: proposed utility
Posted by "Parashuram N (MS OPEN TECH)" <pa...@microsoft.com>.
Looks like a good candidate to discuss at the monthly hangouts ?
-----Original Message-----
From: Staci Cooper [mailto:staci.mcl@gmail.com]
Sent: Wednesday, April 8, 2015 11:05 AM
To: dev@cordova.apache.org
Subject: Re: proposed utility
Did anything ever come of this?
I'd be happy to do some work on this if the consensus is that the implementation needs to be changed.
On Tue, Jan 13, 2015 at 2:10 PM, Staci Cooper <st...@gmail.com> wrote:
> When I was implementing this I initially did add it as a '--local / -l'
> option to the cli. My concern was that it requires the developer to
> have a global installation of Cordova even if all they want is the local command.
> And assuming the user's global and local installs have different
> version numbers, all they would have to do is accidentally omit the -l
> and they would unwittingly use the wrong version of Cordova.
>
> I could add it back in as a flag, or have separate 'cordova' and
> 'cordova-local' commands in the cli. Or were you suggesting changing
> the default behavior of the cordova command to shell out to local? In
> which case we could have a flag to turn that behavior off for
> backwards compatibility... or to fallback to the global version if no
> local version is found. Hm, I'm not sure..
>
> On Fri, Jan 9, 2015 at 4:35 PM, Jesse <pu...@gmail.com> wrote:
>
>> Do we need to start a discussion around cordova-cli plugins?
>>
>> Personally I prefer keeping this in a separate repo.
>>
>> @purplecabbage
>> risingj.com
>>
>> On Fri, Jan 9, 2015 at 1:08 PM, Tommy Williams <to...@devgeeks.org>
>> wrote:
>>
>> > Just as an aside, I have resorted to:
>> >
>> > alias cdv="./node_modules/.bin/cordova"
>> >
>> > Heh.
>> > On 10/01/2015 8:06 am, "Tommy Williams" <to...@devgeeks.org> wrote:
>> >
>> > > +1 for what Michal describes. Better going forward as well as
>> backwards
>> > > compatibility.
>> > >
>> > > Win win?
>> > > On 10/01/2015 7:54 am, "Michal Mocny" <mm...@chromium.org> wrote:
>> > >
>> > >> I like the way gulp works: the same package acts different when
>> > installed
>> > >> globally/locally. Namely, the global always shells work off to
>> > >> the
>> > local.
>> > >>
>> > >> So, instead of a separate cordova-local utility (akin to grunt
>> > >> and grunt-cli), perhaps we just add your feature directly into
>> cordova-cli?
>> > >>
>> > >> For backwards compat, I think we should still allow the global
>> > cordova-cli
>> > >> to do work as we do now (i.e. we don't *require* local
>> > >> installs), but
>> > if a
>> > >> local install happens to exist it would shell out to that.
>> > >>
>> > >> Anyway, neat that you've implemented this already!
>> > >>
>> > >> On Fri, Jan 9, 2015 at 3:41 PM, Staci Cooper
>> > >> <st...@gmail.com>
>> > wrote:
>> > >>
>> > >> > A while ago I made a utility called cordova-local for managing
>> > multiple
>> > >> > local Cordova installations. It's similar to how
>> > >> > grunt/grunt-cli
>> > works;
>> > >> > once installed globally, you run 'cordova-local' instead of
>> 'cordova'
>> > >> and
>> > >> > it will locate and pass its arguments off to the closest
>> installation.
>> > >> >
>> > >> > It's kept and installed independently of the cli but my
>> > >> > initial
>> idea
>> > >> was to
>> > >> > keep it in the cordova-cli repo. Since that would complicate
>> > >> > the tools-release/versioning process I closed that PR and
>> > >> > would like to
>> > >> propose
>> > >> > including it as a new repo. I added some specs and docs and
>> > >> > put it
>> in
>> > a
>> > >> > utilities repo that could be used for similar cli-independent
>> tools,
>> > >> > currently here: https://github.com/stacic/cordova-utility. I
>> > >> > added
>> > some
>> > >> > tests to it and also made PRs for documenting the utility in
>> > >> cordova-docs
>> > >> > <https://github.com/apache/cordova-docs/pull/259> and adding
>> > >> > it to
>> > the
>> > >> > tools release in cordova-coho
>> > >> > <https://github.com/apache/cordova-coho/pull/61>.
>> > >> >
>> > >> > Opinions? Concerns?
>> > >> >
>> > >>
>> > >
>> >
>>
>
>