Correct, they would be building webworks from source during ./bin/create. This solves the problem which we haven't run into yet where webworks doesn't yet, or can't expose something from native and we need to dive down to c via a native plugin.
It also allows us like Tim said to point to a commit or tag and base off of that rather than wait for a WebWorks release. On Wed, Dec 5, 2012 at 2:38 PM, Filip Maj <f...@adobe.com> wrote: > Hey Gord, what's the idea behind this switch? Why do you want to do this? > > And if I understand correctly, users would essentially be building > WebWorks from scratch, with a few modifications (?), on their own machine > the first time they run ./bin/create ? > > On 12/5/12 11:31 AM, "Tim Kim" <timki...@gmail.com> wrote: > > >+1 > > > >I would like to be able to access the latest updates of webworks as > >opposed > >to waiting around for a release to land on the bb webworks download page. > > > > > >On 5 December 2012 11:05, Gord Tanner <gtan...@gmail.com> wrote: > > > >> Currently for developing for BlackBerry 10 the user needs to download > >>and > >> install the WebWorks SDK. [1]. > >> > >> This SDK is opensource and available from github [2] and users are able > >>to > >> clone and build the SDK with the native development tools available [3]. > >> > >> I would like to switch the BlackBerry 10 platform for cordova to use the > >> NDK and clone WebWorks from github. The only difference a cordova > >> developer would notice would be what download we tell them to install in > >> the documentations, everything else would be handled by the ./bin/create > >> script and ./cordova/* scripts pointing where the WebWorks SDK lives. > >> > >> This preps us to have the tools available on the developers machine to > >> build any native extensions that may or may not be needed for > >>BlackBerry 10 > >> development. > >> > >> [1] https://developer.blackberry.com/html5/download/ > >> [2] https://github.com/blackberry/BB10-Webworks-Packager > >> [3] http://developer.blackberry.com/native/beta/ > >> > > > > > > > >-- > >Timothy Kim > >
