Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of brian.leroux@gmail.com
 designates 209.85.161.175 as permitted sender)
MIME-Version: 1.0
Sender: brian.leroux@gmail.com
In-Reply-To: <CC29B58B.A2A2%fil@adobe.com>
References: 
 <CAP7NMPrusWP3t5CAqvj-4q8mnDHu_z5cFp-wGiqojeBZuLmgUA@mail.gmail.com>
	<CC29B58B.A2A2%fil@adobe.com>
Date: Mon, 16 Jul 2012 12:46:16 -0700
Message-ID: 
 <CADVgkyPfJ8Jixo6nVB_zyxgCtFkfwthU1gpTEYMgBGSeEPyzYQ@mail.gmail.com>
Subject: Re: Plugin Development Guide
From: Brian LeRoux <b@brian.io>
To: callback-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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
>