Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AE4DED50F for ; Wed, 10 Oct 2012 00:01:11 +0000 (UTC) Received: (qmail 90770 invoked by uid 500); 10 Oct 2012 00:01:11 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 90743 invoked by uid 500); 10 Oct 2012 00:01:11 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 90735 invoked by uid 99); 10 Oct 2012 00:01:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 00:01:11 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of reinstein.mike@gmail.com designates 209.85.220.175 as permitted sender) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 00:01:05 +0000 Received: by mail-vc0-f175.google.com with SMTP id p1so7746928vcq.6 for ; Tue, 09 Oct 2012 17:00:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=emOJII1rU/C6KWjhtJgAdUAS2j5aUhikAYfrQjtb7i4=; b=RdPBx1eSXiaeRLe3wYOatGwunli3z0d18I38zw6lMeEoNys8MUCJGHMlRx1c9+Cwu6 jjsy5fZrCQgqAi693ZrPzVWIrz2zpCqPvHz+a5YFhtJ8xR/pFzcqyvYtN3b/5nzPGUVY t+AQS1rGGwfCO1eWoQSNPcdHtHenzX3KzUjLMjGYlv2DuYvZ+DGdPgvu59VrDfFrJc6v kC+DZzV5wH9OLhFV9tUXvHntxh84A8ektfJQGk5xaDOAQux76104bEimeloJLWWQ8Hlz 4tFZx4TYwKg5cwai1e9h7bJ8eJ2Ko6ZyZlyTCtX7HZmrseikfL50RIq9qMVDxWK/1Wk7 L2/A== MIME-Version: 1.0 Received: by 10.58.67.134 with SMTP id n6mr2348852vet.11.1349827244571; Tue, 09 Oct 2012 17:00:44 -0700 (PDT) Received: by 10.220.160.139 with HTTP; Tue, 9 Oct 2012 17:00:44 -0700 (PDT) In-Reply-To: References: Date: Tue, 9 Oct 2012 20:00:44 -0400 Message-ID: Subject: Re: Pluginstall tool discussion From: Mike Reinstein To: callback-dev@incubator.apache.org, alunny@gmail.com Content-Type: multipart/alternative; boundary=047d7b2ee7856bbabd04cba9259a --047d7b2ee7856bbabd04cba9259a Content-Type: text/plain; charset=ISO-8859-1 Hi Andrew, I agree on all points. Some additional feedback on a few specifics: > It looks like Mike has made a start on that with his > cordova-pluginrepo repository Correct! Thanks for taking the time to look at it. I'm hoping to have a working prototype by end of week. > The only way to find those problems is to try writing those plugins. Agreed, though I think inspecting existing plugins is a good start too. Have you had a chance to look at my google docs spreadsheet on plugin work? tab 1 is a grid of all plugins and their supported platforms, plus a few bits of meta data. Tab 3 was my attempt to go through some of the more "popular" plugins, analyizing their suitability for packaging via pluginstall. Where it fell short I documented. Green means good to go as-is, red means some issues, yellow means unsure (might be ok.) I'd love some more feedback on this. the doc is globally shared so everyone can modify it. I think we could use tab 3 to coordinate our work and provide visibility. thoughts? -Mike On Tue, Oct 9, 2012 at 7:44 PM, Andrew Lunny wrote: > I've missed most of this discussion, but I wanted to make a few quick > points: > > * `pluginstall` (the tool I developed, that is used by PhoneGap Build) is a > tool for installing plugins. Per the Unix philosophy, it doesn't and won't > do anything other than that. > > * There may well be a need and a demand for a tool that grabs plugins from > git repositories, uninstalls plugins, generates starter plugins, etc. But > that's not pluginstall, and I think that tool should probably be named > something else. It looks like Mike has made a start on that with his > cordova-pluginrepo repository, which is awesome. > > * The problems that need to be solved by pluginstall are of the form "I > can't install plugin x with pluginstall", or "I can't write a plugin that > does x that can be installed by pluginstall." The only way to find those > problems is to try writing those plugins. The PGB team is moving forward on > a few, and we've worked with some other companies who have helped us see > where pluginstall was lacking (adding multiple children to an Android > intent-filter, installing a dylib into an iOS project). > > * node-xcode is a separate project, and will be useful for any plugin tools > written with node. It would probably be better for everyone's sanity if > there was a single version of that parser. I've been pretty slack about > merging changes, so I'll get up to speed on that. > > * If other tools want to interoperate with pluginstall, they should follow > the plugin spec here: > https://github.com/alunny/cordova-plugin-spec > That's a working document and is open to changes. Again, my preference is > for changes of the form "I can't write a plugin that does X in this format" > rather than "this element has a slightly misleading name; how about this > name?". The GitHub issues for that repo is the best place to discuss > changes to that spec. > > Cheers, > Andrew > > On 6 October 2012 09:08, Mike Reinstein wrote: > > > Andrew's is the one used by pg build. Anis has changes from all of us and > > has the most the up to date code: > > > > https://github.com/imhotep/pluginstall > > > > -Mike > > > > > > > > On Sat, Oct 6, 2012 at 8:08 AM, Patrick Mueller > wrote: > > > > > On Sat, Oct 6, 2012 at 5:22 AM, Brian LeRoux wrote: > > > > > > > Think its time we nominated a canonical repo for this. Fil's? > > > > > > > > > > URL please? Are we talking about forks of pluginstall? > > > > > > -- > > > Patrick Mueller > > > http://muellerware.org > > > > > > --047d7b2ee7856bbabd04cba9259a--