I'll leave the cordova-blackberry repo to sort out between you guys and
Lorin.

On 5/17/13 8:44 AM, "Bryan Higgins" <br...@bryanhiggins.net> wrote:

>Thanks for testing all of that Fil!
>
>We've been testing out the changes to cordova-js and plugman this morning
>as well and it all seems to be working great!
>
>Only hiccup is some of our unit tests aren't working with node0.9.9+, but
>that's a different story.
>
>I'd like to see pluginScript merged ASAP. cordova-blackberry also needs
>it's copy of cordova-js updated.
>
>
>On Fri, May 17, 2013 at 11:36 AM, Filip Maj <f...@adobe.com> wrote:
>
>> Hey guys,
>>
>> So with the latest plugman master, latest cordova-js master, and using
>>the
>> "pluginScript" branch from blackberry's fork of cordova-blackberry,
>> everything works great!
>>
>> I was able to successfully build the calendar plugin, install it into my
>> bb10 cordova app with plugman, and add some shit to my calendar on my
>> device from within my app.
>>
>> Really like the flow you guys have for blackberry10 cordova apps. And
>>it's
>> kind of cool to see plugman running under-the-hood to install the core
>> apis when I go to create a new app :)
>>
>> So w.r.t. the earlier issue about XHR'ing to the cordova_plugins.json
>>file
>> and needing it to be absolutely referenced, with the new change in
>> cordova.js, this is no longer necessary. Cordova.js will search through
>> script tags on the current html page for a ref to "cordova.js", and then
>> build up the right path based on the src reference of that script tag.
>> Although we should probably make that more flexible so the file doesn't
>> have to be called cordova.js..
>>
>> Finally: when can we see the pluginScript branch merged fully into
>> cordova-blackberry?
>>
>> On 5/16/13 12:50 PM, "Bryan Higgins" <br...@bryanhiggins.net> wrote:
>>
>> >Thanks Fil!
>> >
>> >Let me know if you need a hand with anything.
>> >
>> >I'd really like to get that pull into cordova-blackberry merged into
>> >master. We can point package.json to the bb10 branch of plugman for
>>now.
>> >
>> >
>> >On Thu, May 16, 2013 at 3:42 PM, Filip Maj <f...@adobe.com> wrote:
>> >
>> >> Hey guys,
>> >>
>> >> I pushed up a bb10 branch of plugman to apache's repo:
>> >>
>> >>
>> 
>>>>https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=shortlo
>>>>g
>> ;
>> >>h=
>> >> refs/heads/bb10
>> >>
>> >>
>> >> Added one more commit to update the design to reflect the changes
>> >> introduced by supporting dependencies.
>> >>
>> >> Now am going to try to get my env setup to test this stuff out
>> >>on-device.
>> >>
>> >> We definitely need to get that xhr-to-cordova_plugins.json-file thing
>> >> resolved before we can merge this back into master.
>> >>
>> >> On 5/16/13 11:05 AM, "Bryan Higgins" <br...@bryanhiggins.net> wrote:
>> >>
>> >> >Hey Fil,
>> >> >
>> >> >You'll need this branch of cordova-blackberry to test everything:
>> >> >
>> >> >https://github.com/apache/cordova-blackberry/pull/14
>> >> >
>> >> >
>> >> >
>> >> >On Thu, May 16, 2013 at 1:39 PM, Filip Maj <f...@adobe.com> wrote:
>> >> >
>> >> >> Thx Lorin!
>> >> >>
>> >> >> On 5/16/13 10:35 AM, "Lorin Beer" <lorin.beer....@gmail.com>
>>wrote:
>> >> >>
>> >> >> >Hey Fil,
>> >> >> >
>> >> >> >check out the BlackBerry plugin repo on github
>> >> >> >https://github.com/blackberry/cordova-blackberry-plugins
>> >> >> >
>> >> >> >
>> >> >> >On Thu, May 16, 2013 at 10:33 AM, Filip Maj <f...@adobe.com>
>>wrote:
>> >> >> >
>> >> >> >> Hey Bryan
>> >> >> >>
>> >> >> >> I am just looking at this stuff now. Thanks for updating the
>>tests
>> >> >>too.
>> >> >> >>
>> >> >> >> Do you have any plugins that I can try on my BB10 device that I
>> >>could
>> >> >> >>test
>> >> >> >> plugman with?
>> >> >> >>
>> >> >> >> On 5/14/13 11:29 AM, "Bryan Higgins" <br...@bryanhiggins.net>
>> >>wrote:
>> >> >> >>
>> >> >> >> >Hey Fil,
>> >> >> >> >
>> >> >> >> >I'll fill in for Jeff since he's away at BB Live this week. We
>> >>just
>> >> >> >> >rebased
>> >> >> >> >the plugman changes. Could you please take a look?
>> >> >> >> >
>> >> >> >> >https://github.com/apache/cordova-plugman/pull/5
>> >> >> >> >
>> >> >> >> >We split this into two commits, one of them affecting other
>> >> >>platforms.
>> >> >> >> >That
>> >> >> >> >was necessary to get plugins loading when the host HTML file
>>was
>> >> >>not in
>> >> >> >> >the
>> >> >> >> >app root.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >On Fri, May 10, 2013 at 2:15 PM, Filip Maj <f...@adobe.com>
>> wrote:
>> >> >> >> >
>> >> >> >> >> Ahh cool lemme know and I can take a look at it / merge it!
>> >> >> >> >>
>> >> >> >> >> On 5/10/13 11:01 AM, "Jeffrey Heifetz"
>> >><jheif...@blackberry.com>
>> >> >> >>wrote:
>> >> >> >> >>
>> >> >> >> >> >There will be a pull request coming, its just running
>>through
>> >> >> >>testing
>> >> >> >> >>atm
>> >> >> >> >> >https://github.com/blackberry/cordova-plugman/pull/2. I
>> expect
>> >> to
>> >> >> >> >> >re-target this to apache in the coming hours.
>> >> >> >> >> >
>> >> >> >> >> >On 13-05-10 1:52 PM, "Filip Maj" <f...@adobe.com> wrote:
>> >> >> >> >> >
>> >> >> >> >> >>Only issue I see is that <source-file> support was removed
>> >>from
>> >> >>the
>> >> >> >> >> >>blackberry platform handler. With <config-file> and
>><asset>
>> >> >> >>elements
>> >> >> >> >> >>being
>> >> >> >> >> >>handled in prepare, this leaves the blackberry platform
>> >>handler
>> >> >> >>empty.
>> >> >> >> >> >>Would we not want some manner of native file / library
>> >>handling
>> >> >>in
>> >> >> >>the
>> >> >> >> >> >>blackberry implementation of plugman?
>> >> >> >> >> >>
>> >> >> >> >> >>On 5/9/13 8:43 PM, "Lorin Beer" <lorin.beer....@gmail.com>
>> >> >>wrote:
>> >> >> >> >> >>
>> >> >> >> >> >>>great, thanks Fil!
>> >> >> >> >> >>>
>> >> >> >> >> >>>
>> >> >> >> >> >>>On Thu, May 9, 2013 at 1:27 PM, Filip Maj <f...@adobe.com>
>> >> >>wrote:
>> >> >> >> >> >>>
>> >> >> >> >> >>>> I will look into these when I'm back in action tomorrow
>> >> >>Lorin.
>> >> >> >> >> >>>>
>> >> >> >> >> >>>> On 5/7/13 8:29 AM, "Lorin Beer"
>><lorin.beer....@gmail.com
>> >
>> >> >> >>wrote:
>> >> >> >> >> >>>>
>> >> >> >> >> >>>> >for those working on plugman/cli:
>> >> >> >> >> >>>> >
>> >> >> >> >> >>>> >the code migration for blackberry's implementation of
>> >> >> >>bb-cordova
>> >> >> >> >>has
>> >> >> >> >> >>>> >begun.
>> >> >> >> >> >>>> >The plan is to merge their new implementation into
>> >> >> >> >> >>>> >apache/blackberry-cordova and apache/cordova-js as
>>soon
>> >>as
>> >> >> >> >>possible.
>> >> >> >> >> >>>> >The blackberry team also has contributions to plugman
>>and
>> >> >>the
>> >> >> >>cli.
>> >> >> >> >> >>>> >Currently, those contribs have been pushed to the
>>apache
>> >> >> >>plugman
>> >> >> >> >> >>>>future
>> >> >> >> >> >>>> >branch, and apache cli future-bb10 branch.
>> >> >> >> >> >>>> >
>> >> >> >> >> >>>> >The changes to plugman seem to be orthogonal, but
>>shout
>> >>at
>> >> >>me
>> >> >> >>if
>> >> >> >> >>they
>> >> >> >> >> >>>>are
>> >> >> >> >> >>>> >breaking future.
>> >> >> >> >> >>>> >
>> >> >> >> >> >>>> >- Lorin
>> >> >> >> >> >>>>
>> >> >> >> >> >>>>
>> >> >> >> >> >>
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >>
>> >> >>
>> 
>>>>>>>--------------------------------------------------------------------
>>>>>>>-
>> >> >> >> >> >This transmission (including any attachments) may contain
>> >> >> >>confidential
>> >> >> >> >> >information, privileged material (including material
>> >>protected by
>> >> >> >>the
>> >> >> >> >> >solicitor-client or other applicable privileges), or
>> >>constitute
>> >> >> >> >> >non-public information. Any use of this information by
>>anyone
>> >> >>other
>> >> >> >> >>than
>> >> >> >> >> >the intended recipient is prohibited. If you have received
>> >>this
>> >> >> >> >> >transmission in error, please immediately reply to the
>>sender
>> >>and
>> >> >> >> >>delete
>> >> >> >> >> >this information from your system. Use, dissemination,
>> >> >> >>distribution, or
>> >> >> >> >> >reproduction of this transmission by unintended recipients
>>is
>> >>not
>> >> >> >> >> >authorized and may be unlawful.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>

Reply via email to