Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of mmocny@google.com designates
 209.85.214.174 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: <E92190E9-E800-4511-910B-B6FA533E004E@redhat.com>
References: <09C96D16-53A6-4E30-9E49-B421A0E12107@gmail.com>
 <CAEeF2Td94BQVrqOLcG1nc7GOnbD8pP8+MbkEnny6uC6JL_h1tw@mail.gmail.com>
 <CANpVHHzyGYnAbRCBx0O55eXn-s=56E4ms-CYnt7V8K-K3WE5gw@mail.gmail.com>
 <CADVgkyNJReeGRy8_puPnxe8m0j+qWiydgXWVyDfeA3G+nCF2Cg@mail.gmail.com>
 <CANpVHHxUyNT0T6363L03OFF0U-uB_6CfcHXdypZKTEO=Q2wJsw@mail.gmail.com>
 <CADVgkyP_ydt=EYxsCROL=PpS4W5=quMNLYtKev4CQkxD8y8fhQ@mail.gmail.com>
 <2d9f1f4ecbd948fb9619904e450be97d@BN1PR07MB135.namprd07.prod.outlook.com>
 <CAMk5LLmGB59AcFBRjQbaGHfoNqu32FeOpGHHE3ovuJsk+WcP3A@mail.gmail.com>
 <CAK_TSXJWtzU=xPz8FQeNw8aKtGbmBYjG8Jxqc2-Jwr4=g28XvQ@mail.gmail.com>
 <CAEeF2TfGTa7GJjLfnUNLszFKnES4cvoebaH3Mv7qdCsZUTiYqw@mail.gmail.com>
 <CANpVHHz-x8MCHXd1toV9_duvoWnLrm0xYjmE-EEF+Wjui7rcWA@mail.gmail.com>
 <77E55741-26EB-4F61-940E-8481F70CD2F1@gmail.com>
 <E92190E9-E800-4511-910B-B6FA533E004E@redhat.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Fri, 20 Sep 2013 06:57:19 -0700
Message-ID: 
 <CAEeF2TfZaX2-CJmrZW-U7-+U0kvTPjwz=g=SqS7kamDpObuNoA@mail.gmail.com>
Subject: Re: What's your daily workflow for cordova development?
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=001a1133073ac0bb6304e6d10d1f

--001a1133073ac0bb6304e6d10d1f
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

plugman create could be used outside of a project, and cordova plugin
create should be used only inside of a project?

All other cordova commands must be used inside a project (except the
"create" entry point), and if we decide to ship the plugin templates with
platforms, and/or decide to make the global cordova command just a
grunt-cli like thing, etc etc, then I would worry about adding uses for
cordova command in some global context.


On Fri, Sep 20, 2013 at 6:42 AM, Lucas Holmquist <lholmqui@redhat.com>wrote=
:

> So currently when doing
>
> $ cordova plugin =85.
>
> it fails if you are not in a cordova project.
>
> but
>
> $ cordova plugin create
>
> might not be used inside a project( i think it shouldn't be used inside a
> project at all,  but i can be convinced otherwise )
>
>
> On Sep 4, 2013, at 10:46 PM, lmnbeyond <lmnbeyond@gmail.com> wrote:
>
> >
> >
> >> I also think it should sub-shell to a platform script. We already have
> >> a `project template` folder in each platform. We can easily add a
> >> `plugin template` as well and write a quick create_plugin script.
> >>
> >> What do you guys think of the workflow I described above ? Any
> >> comments ? I can create jira issues for it and tackle it.
> >>
> >> -a
> >>
> >
> > Hi Anis,
> >
> > I just want to confirm whether or not this is the workflow we are
> talking about :
> >
> > For a brand new plugin:
> >
> > $ cordova plugin create /path/to/myPlugin
> > $ cordova plugin add /path/to/myPlugin --watch
> >
> >
> > For an existing plugin:
> >
> > $ cordova plugin add /path/to/corePlugin --watch
> >
> >
> > Although, I'm not quite clear about the complexity behind this,  I thin=
k
> the above workflow is great for me!
> >
> >
> >
> >
> >
> >
>
>

--001a1133073ac0bb6304e6d10d1f--