Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.78 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Mon, 28 Jan 2013 10:40:54 -0800
Subject: Re: best practice plugin authoring guidelines / window.plugins hate
Thread-Topic: best practice plugin authoring guidelines / window.plugins hate
Thread-Index: Ac39hodonFaOEIRWRguaplFE/la/GA==
Message-ID: <CD2C0600.168DD%fil@adobe.com>
In-Reply-To: 
 <CADVgkyMk7xqibLtZ2GLWZc+cdjQ3aNBx3CH6r4ovcsUJf8yYtQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.5.121010
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Don't think so. Should be up to the user. That said Cordova should provide
a registration mechanism to enable collision detection (I think Andrew
Grieve has something like this in his symbol mapping branch in cordova-js).

On 1/28/13 10:34 AM, "Brian LeRoux" <b@brian.io> wrote:

>The community is starting to put plugins in their own repos (good). I
>noticed this one today:
>
>https://github.com/vstirbu/InstagramPlugin
>
>(Awesome.)
>
>But I can't stand window.plugins any longer. I think this might be a
>hangover from the existing plugin space but not totally sure---is
>there a good reason to have the plugins global "namespace" anymore?