... Why?
On 7/17/12 1:44 AM, "Tommy Williams" wrote:
>+1
>
>> p.s
>> REALLY want good docs on plugins for 2.0 on release - seen the changes
>>to
>> Cordova2.0 and really freaked out right now... :p
>>
>
+1
> p.s
> REALLY want good docs on plugins for 2.0 on release - seen the changes to
> Cordova2.0 and really freaked out right now... :p
>
@Brian
> would like to see a convention encouraged wherein plugins are called
cordova-plugin-whatever-whatever
^ With you on that...
:)
https://github.com/Wizcorp/phonegap-plugin-apsalar
https://github.com/Wizcorp/phonegap-plugin-localNotifications
https://github.com/Wizcorp/phonegap-plugin-wizSp
Following the convention of the core APIS, the module id should be:
cordova/plugin/foo
On 7/16/12 3:10 PM, "Don Coleman" wrote:
>I like the idea of an echo plugin. I might switch my phonegap day
>example from cordova-plugin-helloworld to cordova-plugin-echo
>
>Any suggested naming conventions
I like the idea of an echo plugin. I might switch my phonegap day
example from cordova-plugin-helloworld to cordova-plugin-echo
Any suggested naming conventions for the JavaScript module?
cordova.define("foo", function() {});
foo
/plugin/foo
/cordova/plugin/foo
On Mon, Jul 16, 2012 at 5:48 PM,
This is all sounding really good. Looking forward to a better day for plugin
devs.
Congrats on all your hard work.
On 17/07/2012, at 5:54, Michael Brooks 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
Me likey.
On 7/16/12 1:29 PM, "Michael Brooks" wrote:
>+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 wrote:
>
>> agree. also: would like to start a convention here we
+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 wrote:
> agree. also: would like to start a convention here we discussed some time
> ago.
>
> platforms and cordova core stuff are al
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
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
sh
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 wrote:
> Great stuff Mike, thanks.
>
> I think for the easy win, we host it under an "example-plugin" folder o
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:
12 matches
Mail list logo
