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.29 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Tue, 26 Mar 2013 17:19:03 -0700
Subject: Re: [plugman] js install
Thread-Topic: [plugman] js install
Thread-Index: Ac4qgLIPwjkDYXIOTrWu+3SrOlsUeQ==
Message-ID: <CD7788B0.1B77A%fil@adobe.com>
In-Reply-To: 
 <CADVgkyM+KfVuvC8ivXN3T5_p3zohS4O7y0_ZLkZ7DecuEVxUzw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

FYI, I've added a bunch of issues based on a brain dump of outstanding
tasks that Braden wrote up in plugman's future branch. Tagged the issues
in JIRA as "future", and they are also noted at the bottom of
plugman/future FUTURE.md under the TODO section. We're pretty damn close
but missing tests for all the new features, but I think close to 2.6
release time this stuff should be ready..

Super exciting!!

On 3/26/13 10:23 AM, "Brian LeRoux" <b@brian.io> wrote:

>fuckin eh, sounds awesome---thx man
>
>On Tue, Mar 26, 2013 at 10:14 AM, Braden Shepherdson
><braden@chromium.org> wrote:
>> I added the plugin-loading code there (see scripts/plugin_loader.js)
>>but I
>> wasn't aware that XHRs to file:// URLs always have status 0 instead of
>> 200/404/etc. Andrew fixed that today, but we decided not to try to
>> cherry-pick that change into 2.6.x.
>>
>> It's harmless for the main function of cordova-js, but it means that the
>> future branch of the CLI tools won't work with the released 2.6.
>>
>> Braden
>>
>>
>> On Tue, Mar 26, 2013 at 12:57 PM, Brian LeRoux <b@brian.io> wrote:
>>
>>> Braden: whats happening in cordova-js that is broken/being heavily
>>> refactored?
>>>
>>>
>>> On Tue, Mar 26, 2013 at 9:36 AM, Braden Shepherdson
>>><braden@chromium.org>
>>> wrote:
>>> > You'll need the future branch of cordova-cli and plugman, and to go
>>> through
>>> > a bit of a dance to get those two installed and npm linked properly.
>>>The
>>> > dance is as follows:
>>> >
>>> > cd plugman
>>> > npm install
>>> > sudo npm link
>>> > cd ../cordova-cli
>>> > npm install
>>> > sudo npm link
>>> > npm link plugman
>>> >
>>> > Now when you run 'cordova' you get the git version, and 'plugman'
>>> likewise.
>>> > You can skip everything after the first three lines if you're only
>>>using
>>> > plugman and not CLI.
>>> >
>>> > Note that the master branch is currently broken with cordova-js
>>>2.6.0;
>>> > you'll have to use the future branch. Unfortunately that branch is
>>>under
>>> > heavy development right now, but I'm trying to keep it in a working
>>> state.
>>> >
>>> > Braden
>>> >
>>> >
>>> > On Tue, Mar 26, 2013 at 12:16 PM, Filip Maj <fil@adobe.com> wrote:
>>> >
>>> >> Use the future branch of plugman. That's where braden is putting the
>>> >> symbol mapping work into.
>>> >>
>>> >> On 3/26/13 9:09 AM, "Brian LeRoux" <b@brian.io> wrote:
>>> >>
>>> >> >Steve has plugman working with devicemotion plugin. Happy days! Its
>>> >> >time he ripped the JS out of cordova-js and put it in the plugin.
>>>But
>>> >> >does plugman support js installation? What needs happening to make
>>>it
>>> >> >so?
>>> >>
>>> >>
>>>