Personally, I don't think this should be built into the system; I see
nothing wrong with the workflow that Anis originally posted.
If all we ever did was write echo plugins, then this would make sense, but
IMHO, actually writing a plugin requires some time spent in each ./platform

As an example:
I am currently working through some missing functionality on WP7+8 for the
filetransfer plugin.
I have created a new project, installed the filetransfer plugin, and added
the specs/tests so when I run it I jump right to the tests.
I now have visual studio open, and I have deleted the FileTransfer.cs file
from the project, and simply sim-linked to the one in the plugin repo. When
I am satisfied that everything works, I will simply commit the plugin repo
and be done ...








@purplecabbage
risingj.com


On Wed, Sep 4, 2013 at 4:56 PM, Anis KADRI <anis.ka...@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
>
> On Wed, Sep 4, 2013 at 7:26 AM, Michal Mocny <mmo...@chromium.org> wrote:
> > Maybe a plugin template ships with each platform, and when you "plugin
> > create" it merges the template for each platform you have installed?
> >
> > That would mean you have to add all interested platforms before creating
> a
> > plugin.
> >
> > -Michal
> >
> >
> > On Wed, Sep 4, 2013 at 10:22 AM, Ian Clelland <iclell...@chromium.org
> >wrote:
> >
> >> On Tue, Sep 3, 2013 at 11:50 AM, Braden Shepherdson <
> bra...@chromium.org
> >> >wrote:
> >>
> >> > On Tue, Sep 3, 2013 at 11:07 AM, Jonathan Bond-Caron <
> >> > jbo...@gdesolutions.com> wrote:
> >> > > Two new features could be useful from cli:
> >> > > a) Create an initial plugin from a template
> >> > > cordova plugin create [path] [name]
> >> > >
> >> > > e.g.
> >> > > > cordova plugin create F:/GitHub/MyPlugin MyPlugin
> >> > >
> >> > >
> >> > I agree, this would be useful. It's pretty easy to implement, just
> not a
> >> > high priority. Do you want to file a JIRA ticket for it?
> >> >
> >>
> >> +1 for scaffolding; this could be very useful as a means of documenting
> >> best practices for plugin authors.
> >>
> >> I'm not certain how this interacts with platforms, though -- would we
> have
> >> a monolithic "plugin template" that contains a skeleton for each
> platform,
> >> or is there some kind of cooperation between the various platform repos
> so
> >> that they can contribute their own code to the template? (or maybe the
> >> default is JS only, and you have to know how to add code for any given
> >> platform that you develop for)
> >>
> >> Ian
> >>
>

Reply via email to