Re: 3rd party Plugin code structure

2013-01-03 Thread Brian LeRoux
Yup, that'd be a good start. Its becoming a big topic. Arguably these are discreet/different things (authoring / packaging). (Aside: do we have a way to validate a package?) Once we have those the next thing is documenting Publishing/Discovery. On Thu, Jan 3, 2013 at 11:59 AM, Filip Maj wrote:

Re: 3rd party Plugin code structure

2013-01-03 Thread Filip Maj
Why not iterate on the existing Plugin Development Guide [1] ? http://docs.phonegap.com/en/2.2.0/guide_plugin-development_index.md.html#Pl ugin%20Development%20Guide On 1/3/13 11:55 AM, "Brian LeRoux" wrote: >I think we should add a Guide for Plugin Packaging --- things will >move quicker, and

Re: 3rd party Plugin code structure

2013-01-03 Thread Brian LeRoux
I think we should add a Guide for Plugin Packaging --- things will move quicker, and b/c src is more canonical it is more likely to encourage contrib. On Thu, Jan 3, 2013 at 11:46 AM, Filip Maj wrote: > Go with Anis' (imhotep) plugman tool as the defacto plugin installation > tool, until we get i

Re: 3rd party Plugin code structure

2013-01-03 Thread Filip Maj
Go with Anis' (imhotep) plugman tool as the defacto plugin installation tool, until we get it into an Apache repo (probably cordova-cli?). It was based on Andrew's plugin spec and pluginstall tool but started deviating slightly once we (Cordova) wanted to support more robust use cases (uninstallati

Re: 3rd party Plugin code structure

2012-12-27 Thread Michal Mocny
I do not mean that one or the other is incorrect, but there are small differences in content and text formatting. Small matter for sure, but since they are being modified independently I wasn't sure which is the "right" version to point to (esp since both readme's claim to not be official cordova

Re: 3rd party Plugin code structure

2012-12-22 Thread Anis KADRI
Could you elaborate a little bit on the differences ? On Thu, Dec 20, 2012 at 12:18 PM, Michal Mocny wrote: > So the docs in https://github.com/imhotep/plugman differ slightly from > https://github.com/alunny/cordova-plugin-spec > > And the Readme in phonegap-plugin doesn't do a good job of poi

Re: 3rd party Plugin code structure

2012-12-20 Thread Michal Mocny
So the docs in https://github.com/imhotep/plugman differ slightly from https://github.com/alunny/cordova-plugin-spec And the Readme in phonegap-plugin doesn't do a good job of pointing the right place to look (other than indirectly through Shaz's post). Shall I add a line to the readme pointing t

Re: 3rd party Plugin code structure

2012-12-20 Thread Don Coleman
+1 for using Andrew's cordova-plugin-spec On Thu, Dec 20, 2012 at 2:52 PM, Brian LeRoux wrote: > This is pretty close to Lunny's pluginstall spec: > > https://github.com/alunny/cordova-plugin-spec > > For which the tools are being built. View the current > phonegap/phonegap-plugins repo as a st

Re: 3rd party Plugin code structure

2012-12-20 Thread Brian LeRoux
This is pretty close to Lunny's pluginstall spec: https://github.com/alunny/cordova-plugin-spec For which the tools are being built. View the current phonegap/phonegap-plugins repo as a stepping stone. It bought us time to sorted out our own backyard before inviting everyone in to play. =) On T

Re: 3rd party Plugin code structure

2012-12-20 Thread Michal Mocny
Oh right, I remember seeing some of that doc when Mike was poking around. Thanks for the links/refresher! -Michal On Thu, Dec 20, 2012 at 2:44 PM, Shazron wrote: > I think the phonegap-plugins repo structure was way before we decided to > organize it better, ie the plugin spec. More details h

Re: 3rd party Plugin code structure

2012-12-20 Thread Shazron
I think the phonegap-plugins repo structure was way before we decided to organize it better, ie the plugin spec. More details here, with some example plugins used by PG Build: http://shazronatadobe.wordpress.com/2012/11/07/cordova-plugins-put-them-in-your-own-repo-2/ I think for Cordova the ongoin

3rd party Plugin code structure

2012-12-20 Thread Michal Mocny
Seems that our thirdparty plugins are platform-centric; with javascript not written to be shared across platforms. Even if individual contributors are not willing to write implementations for other platforms, or if a plugin only really applies to a single platform, I think we should still provide