WRT to BlackBerry since node is already required, it's not an "extra" dependency. The other thread is related to Android (and possibly iOS/windows).
As long as the new BB repo supports: 1. Plugin design and documentation on how to do so 2. Command line scripts [1] 3. Can run mobile spec and passes at a reasonable rate .. Im happy [1] http://wiki.apache.org/cordova/CommandLineToolingDesign On 4/15/13 9:45 AM, "Lorin Beer" <[email protected]> wrote: >First steps are to bring your repo in line with the current workflow and >cross platform tool chain. >A for instance is the create script: the other platforms use bash scripts >for the 'create' command, and BlackBerry's BB10 repo is dependent on Node. >There is an ongoing discussion on the list concerning node as a dependency >for our build toolchain, which I would encourage you to chime in on. > > > >On Mon, Apr 15, 2013 at 9:09 AM, Jeffrey Heifetz ><[email protected]>wrote: > >> So now that the code has been out for a bit we'd like to start talking >> about getting the code into the 2.7 release. >> >> There are no longer any hacks or hoops to getting it running and anyone >> interested can try it out. Mobile spec results are about on par with the >> previous implementation and will continue to improve as we re-implement >> plugins. >> >> So what is the process for getting a large number of commits into >>multiple >> repos? >> >> >> On 13-04-08 1:39 PM, "Ken Wallis" <[email protected]> wrote: >> >> >To a degree I think the architecture has been simplified. Was not the >> >Cordova APIs calling to WebWorks apis, which then hit native, whereas >>now >> >we don't have the WebWorks layer? >> >-- >> > >> >Ken Wallis >> > >> >Product Manager WebWorks >> > >> >BlackBerry >> > >> >289-261-4369 >> > >> >________________________________________ >> >From: [email protected] [[email protected]] on behalf of >>Chris >> >DelCol [[email protected]] >> >Sent: Monday, April 08, 2013 10:15 AM >> >To: [email protected] >> >Subject: Re: BlackBerry BB10 Repos on GitHub >> > >> >I think the biggest impact is that the architecture and features of >> >Cordova >> >are now implemented directly, rather than through a proprietary SDK >>that >> >is >> >"somewhat" aligned. I'm not sure there will be actual performance >>gains, >> >or >> >that the architecture is easier. But what it does mean is that >> >compatibility should go way up, and focus on it will go up as well >>since >> >we >> >are not split between 2 competing products. >> > >> > >> >On Mon, Apr 8, 2013 at 12:09 PM, Michal Mocny <[email protected]> >> wrote: >> > >> >> This sounds pretty cool. >> >> >> >> For those with no prior BB experience, is there a high level summary >>of >> >>the >> >> net effect of the changes? x% faster exec, N less bytes of binary, Y >> >> timesr >> >> easier plugin development etc? >> >> >> >> Thanks, >> >> -Michal >> >> >> >> >> >> On Mon, Apr 8, 2013 at 11:22 AM, Bryan Higgins >><[email protected] >> >> >wrote: >> >> >> >> > It's exactly the same as this extension, but we've converted it >>into a >> >> > cordova plugin. We'll provide both the source and pre-compiled >> >>libraries. >> >> > >> >> > >> >> >> >> >> >>https://github.com/blackberry/BB10-WebWorks-Framework/tree/master/ext/jpp >> >>s >> >> > >> >> > >> >> > On Mon, Apr 8, 2013 at 10:57 AM, Lorin Beer >><[email protected] >> >> > >wrote: >> >> > >> >> > > sounds great Bryan, >> >> > > >> >> > > about the private native dependency, is that provided as a >> >>precompiled >> >> > > library? >> >> > > Can we run these codes? >> >> > > >> >> > > - Lorin >> >> > > >> >> > > >> >> > > On Mon, Apr 8, 2013 at 7:13 AM, Bryan Higgins >> >><[email protected] >> >> > > >wrote: >> >> > > >> >> > > > Sounds good! There are still a few things we need to finish up >>to >> >>get >> >> > > test >> >> > > > results in line with the existing implementation. File API is >>the >> >>big >> >> > > one. >> >> > > > >> >> > > > There is also a native library needed which is in the private >>repo >> >> > right >> >> > > > now. We'll look at moving that into cordova-blackberry. >> >> > > > >> >> > > > >> >> > > > On Mon, Apr 8, 2013 at 9:52 AM, Lorin Beer >> >><[email protected] >> >> > >> >> > > > wrote: >> >> > > > >> >> > > > > Great! Last week, I wrote a little script to provide unique >> >>tags to >> >> > the >> >> > > > > unit tests in mobile spec. Once those are tagged, I'll be >> >>pushing >> >> up >> >> > > the >> >> > > > > currently failing tests in the existing BB10 implementation. >> >>Having >> >> > > those >> >> > > > > tests documented will hopefully provide an anchor to move the >> >> > > discussion >> >> > > > > forward. >> >> > > > > >> >> > > > > >> >> > > > > On Mon, Apr 8, 2013 at 5:57 AM, Bryan Higgins < >> >> > [email protected] >> >> > > > > >wrote: >> >> > > > > >> >> > > > > > I'll follow up today with that. There are a few people who >> >>need >> >> to >> >> > > sign >> >> > > > > > still. >> >> > > > > > >> >> > > > > > >> >> > > > > > On Sun, Apr 7, 2013 at 6:32 PM, Lorin Beer < >> >> > [email protected] >> >> > > > >> >> > > > > > wrote: >> >> > > > > > >> >> > > > > > > This is great stuff! I figured we'd be waiting for a >>while >> >> > longer, >> >> > > > > great >> >> > > > > > to >> >> > > > > > > see this go live! >> >> > > > > > > Tim and I will be going through this right away. >> >> > > > > > > Bryan, I know you are on the >> >> > > > > > > list< >> >> https://people.apache.org/committer-index.html#unlistedclas >> >> > >; >> >> > > > has >> >> > > > > > > the rest of your team signed the Apache CLA as well? >> >> > > > > > > >> >> > > > > > > - Lorin >> >> > > > > > > >> >> > > > > > > On Sat, Apr 6, 2013 at 9:53 AM, Tim Kim >><[email protected] >> > >> >> > > wrote: >> >> > > > > > > >> >> > > > > > > > Awesome! >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > > On 6 April 2013 08:16, Ken Wallis >><[email protected] >> > >> >> > > wrote: >> >> > > > > > > > >> >> > > > > > > > > So awesome to see this go live, thanks Bryan. Looking >> >> forward >> >> > > to >> >> > > > > > seeing >> >> > > > > > > > > progress towards this being merged into the Apache >> >>repos! >> >> > > > > > > > > >> >> > > > > > > > > Sent from my BlackBerry Z10 smartphone. >> >> > > > > > > > > From: Bryan Higgins >> >> > > > > > > > > Sent: Saturday, April 6, 2013 6:42 AM >> >> > > > > > > > > To: [email protected] >> >> > > > > > > > > Reply To: [email protected] >> >> > > > > > > > > Subject: BlackBerry BB10 Repos on GitHub >> >> > > > > > > > > >> >> > > > > > > > > >> >> > > > > > > > > Over the last few weeks, we at BlackBerry WebWorks >>have >> >> been >> >> > > > > working >> >> > > > > > > on a >> >> > > > > > > > > prototype for a new version of our SDK based on >>Cordova. >> >> I'm >> >> > > > happy >> >> > > > > to >> >> > > > > > > say >> >> > > > > > > > > that we're now able to share our repos publicly! >> >> > > > > > > > > >> >> > > > > > > > > To understand what we've done, you will first need to >> >> > > understand >> >> > > > > that >> >> > > > > > > > > WebWorks for BB10 is really 3 things: >> >> > > > > > > > > >> >> > > > > > > > > 1. Packager (bbwp) a set of node scripts to >> >>assemble >> >> > apps >> >> > > > from >> >> > > > > > > > source >> >> > > > > > > > > 2. Framework handles bootstrap, extension >>loading, >> >> exec >> >> > > > calls, >> >> > > > > > > > events >> >> > > > > > > > > 3. Extensions all of the APIs. Similar to >>cordova >> >> > plugins, >> >> > > > but >> >> > > > > > > > > included in the SDK rather than directly in the >>project. >> >> > > > > > > > > >> >> > > > > > > > > All of this is built on top of the "web platform" - a >> >>layer >> >> > on >> >> > > > top >> >> > > > > of >> >> > > > > > > > > WebKit which exposes device APIs. We plan to document >> >>this >> >> > > layer >> >> > > > > and >> >> > > > > > > > > provide instructions on how to build a web platform >>app >> >> using >> >> > > > only >> >> > > > > > the >> >> > > > > > > > NDK. >> >> > > > > > > > > >> >> > > > > > > > > For those wanting a rich set of APIs, we will >>provide a >> >> > Cordova >> >> > > > > build >> >> > > > > > > > along >> >> > > > > > > > > with a set of custom plugins for platform features. >> >> > > > > > > > > >> >> > > > > > > > > To get to that world, we need to move some logic from >> >>the >> >> > > > packager >> >> > > > > > and >> >> > > > > > > > > framework into Cordova. This will really simplify the >> >>exec >> >> > > chain >> >> > > > > and >> >> > > > > > > ease >> >> > > > > > > > > plugin development. >> >> > > > > > > > > >> >> > > > > > > > > Old world: >> >> > > > > > > > > Plugin script > cordova.exec > WebWorks extension > >> >> > > > webworks.exec > >> >> > > > > > web >> >> > > > > > > > > platform / native >> >> > > > > > > > > >> >> > > > > > > > > New world: >> >> > > > > > > > > Plugin script > cordova.exec > web platform / native >> >> > > > > > > > > >> >> > > > > > > > > All of our repos are up at github.com/blackberry. >> >>Here's a >> >> > > quick >> >> > > > > > > summary >> >> > > > > > > > > of >> >> > > > > > > > > what we have done so far. >> >> > > > > > > > > >> >> > > > > > > > > https://github.com/blackberry/cordova-blackberry >> >> > > > > > > > > >> >> > > > > > > > > * split out BB10 from BBOS/PlayBook >> >> > > > > > > > > * Re-implemented cordova create, build and run in >> >>node, >> >> > > using >> >> > > > > > libs >> >> > > > > > > > from >> >> > > > > > > > > our packager >> >> > > > > > > > > * Introduced "target" script for managing device >>and >> >> > > > simulator >> >> > > > > > > > > configuration >> >> > > > > > > > > * Started the process of converting core plugins >> >>from >> >> > > > wrappers >> >> > > > > to >> >> > > > > > > > > calling web platform directly >> >> > > > > > > > > >> >> > > > > > > > > https://github.com/blackberry/cordova-js >> >> > > > > > > > > >> >> > > > > > > > > * Created blackberry10 as a top level platform >> >> > > > > > > > > * Added some bootstrap, exec and event logic from >> >>our >> >> > > > Framework >> >> > > > > > > > > * Started the process of removing the wrappers >>(at >> >> which >> >> > > > point >> >> > > > > > > > > cordova.exec and webworks.exec are merged and >>webworks >> >> events >> >> > > > will >> >> > > > > go >> >> > > > > > > > away) >> >> > > > > > > > > >> >> > > > > > > > > https://github.com/blackberry/cordova-plugman >> >> > > > > > > > > >> >> > > > > > > > > * Copy "controller" code (index.js) and native >>.so >> >> files >> >> > > into >> >> > > > > the >> >> > > > > > > > > project >> >> > > > > > > > > * Implemented our prototype of script injection >> >> (wrapping >> >> > > > > > > js-modules >> >> > > > > > > > in >> >> > > > > > > > > cordova.define and generating plugins.json). >> >> > > > > > > > > >> >> > > > > > > > > https://github.com/blackberry/cordova-cli >> >> > > > > > > > > >> >> > > > > > > > > * Minor changes to support splitting out BB10 >>from >> >>BBOS >> >> > > > > > > > > >> >> > > > > > > > > >> >> https://github.com/blackberry/cordova-blackberry-plugins(not >> >> > > > yet >> >> > > > > > > > public,) >> >> > > > > > > > > >> >> > > > > > > > > * Plugins for BB10 platform features >> >> > > > > > > > > >> >> > > > > > > > > I know this is a lot of dump on the list at once, but >> >>Jeff >> >> > and >> >> > > I >> >> > > > > are >> >> > > > > > > here >> >> > > > > > > > > to answer any questions or concerns. Now that the >>repos >> >>are >> >> > > live >> >> > > > > we'd >> >> > > > > > > > like >> >> > > > > > > > > to start a discussion on getting the code into >>Apache. >> >> We've >> >> > > got >> >> > > > a >> >> > > > > > > small >> >> > > > > > > > > team here working on this (intros to come) and >>everyone >> >>is >> >> > > > excited >> >> > > > > to >> >> > > > > > > > start >> >> > > > > > > > > working with the community. >> >> > > > > > > > > >> >> > > > > > > > > Cheers, >> >> > > > > > > > > Bryan >> >> > > > > > > > > >> >> > > > > > > > > >> >> > > > > >> >> --------------------------------------------------------------------- >> >> > > > > > > > > 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. >> >> > > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > > -- >> >> > > > > > > > Timothy Kim >> >> > > > > > > > >> >> > > > > > > >> >> > > > > > >> >> > > > > >> >> > > > >> >> > > >> >> > >> >> >> > >> >--------------------------------------------------------------------- >> >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. >> >> >> --------------------------------------------------------------------- >> 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. >>
