Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.31 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Mon, 16 Jul 2012 15:16:59 -0700
Subject: Re: Plugin Development Guide
Thread-Topic: Plugin Development Guide
Thread-Index: Ac1joFSdR2aVNFNuT/66tywTnPZCpw==
Message-ID: <CC29E0DD.A321%fil@adobe.com>
In-Reply-To: 
 <CAM2q_UzniZTLazkqycfeyS7zqxiL_yyL6k1xAYYxGJ0GbcjGqQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Following the convention of the core APIS, the module id should be:

cordova/plugin/foo

On 7/16/12 3:10 PM, "Don Coleman" <don.coleman@gmail.com> 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 for the JavaScript module?
>
>cordova.define("foo", function() {});
>
>foo
>/plugin/foo
>/cordova/plugin/foo
>
>On Mon, Jul 16, 2012 at 5:48 PM, Tommy-Carlos Williams
><tommy@devgeeks.org> wrote:
>> 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 <michael@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 <fil@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" <michael@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
>>>>>
>>>>