+1 to the convention. Platform / Supporting Lib: cordova-xxx
Plugin: cordova-plugin-xxx Demo App: cordova-app-xxx On Mon, Jul 16, 2012 at 1:13 PM, Brian LeRoux <b...@brian.io> wrote: > agree. also: would like to start a convention here we discussed some time > ago. > > platforms and cordova core stuff are all named cordova-whatever-whatever > > would like to see a convention encouraged wherein plugins are called > cordova-plugin-whatever-whatever > > no major benefit other than symmetry which is nice to have =) > > On Mon, Jul 16, 2012 at 12:54 PM, Michael Brooks > <mich...@michaelbrooks.ca> wrote: > > My original thought is that the cordova-cli tool should be able to > create a > > plugin with a given name. The created plugin will also be the echo > example, > > since it sets up all scaffolding required to start implementing your own > > plugin. When the echo plugin is available under it's own repository, it > > should be easy for the CLI tool to consume this plugin. > > > > Michael > > > > On Mon, Jul 16, 2012 at 12:46 PM, Brian LeRoux <b...@brian.io> wrote: > > > >> like it, another nice thing about that echo plugin is a baseline for > >> benching the bridge perf; fil should this tie into the cordova-cli > >> stuff? > >> > >> On Mon, Jul 16, 2012 at 12:13 PM, Filip Maj <f...@adobe.com> wrote: > >> > Great stuff Mike, thanks. > >> > > >> > I think for the easy win, we host it under an "example-plugin" folder > or > >> > something of the like in the platform repos this week. > >> > > >> > I can aggregate these into a labs branch and add in support for the > >> > cordova plugin spec, structure the code appropriately, etc. > >> > > >> > On 7/16/12 11:41 AM, "Michael Brooks" <mich...@michaelbrooks.ca> > wrote: > >> > > >> >>Hello guys, > >> >> > >> >>The plugin development guide exists as issue CB-862 [1] with sub-tasks > >> for > >> >>each plugin. > >> >> > >> >>Immediate Goal: > >> >> > >> >>The goal is the walk the user through developing a simple "Hello > Cordova" > >> >>plugin. > >> >> > >> >>In issue CB-862, I've proposed walking the user through the creation > of a > >> >>"Cordova Echo" plugin that simply returns the same string that it was > >> >>called with. This shows the user the plugin's invoke cycle and > condenses > >> >>it > >> >>into an example that uses minimal code. > >> >> > >> >>Source Code: > >> >> > >> >>It would be nice if we can host these plugins somewhere. Thoughts on > >> >>where? > >> >>Platform repo? Labs branch for each plugin? Common labs branch that > uses > >> >>the plugin specification draft [2]? > >> >> > >> >>Longer-term Goal: > >> >> > >> >>Later on, we can expand this guide into a plugin development section > that > >> >>is a complete reference for native constants, accepting and returning > >> >>various formats (string, number, json, array, etc). > >> >> > >> >>Michael > >> >> > >> >>[1] https://issues.apache.org/jira/browse/CB-862 > >> >>[2] https://github.com/alunny/cordova-plugin-spec > >> > > >> >
