Yeah the only issue with plugin.xml is that it's ....XML :-D It would be so much easier to have it stored in JSON. We can make plugman parse the XML from a remote source but I would rather store everything in JSON.
Also there can be multiple versions of plugin.xml. I think that is a good enough reason to store the relevant data about plugins (compatible cordova versions with a given plugin version, dependencies, etc...) in an easy-to-read format (JSON). There is a bit of duplication yes but it's for a good cause and the gain is huge. The submission process would be: - A plugin author submits a new plugin, gives it a version and specifies which version of cordova it was tested on. - A new version of Cordova comes out and requires the plugin author to update their plugin to stay compatible. - We start building the Cordova version <=> plugin version mapping like that. Thoughts ? -a On Fri, Mar 22, 2013 at 2:16 PM, Brian LeRoux <b...@brian.io> wrote: > makes sense to me; we'll likely want to query on that stuff eventually > > On Fri, Mar 22, 2013 at 11:53 AM, Michal Mocny <mmo...@chromium.org> > wrote: > > Should the universe just keep a copy of a plugin.xml so that it can have > a > > list of plugin dependancies and everything? plugin.xml will already > have a > > list of compatible cordova versions, right? > > > > Then the universe can manage a reverse mapping if it wants fast access. > > > > -Michal > > > > > > On Fri, Mar 22, 2013 at 2:00 PM, Brian LeRoux <b...@brian.io> wrote: > > > >> A plugin should specify the Cordova versions it supports too. > >> > >> On Fri, Mar 22, 2013 at 10:59 AM, Brian LeRoux <b...@brian.io> wrote: > >> > I am sure we all agree to this. Want to get a sense of how it will > >> > happen. Anis you mentioned you need Braden to commit the JS stuff > >> > first? > >> >
