Just tested setting this up on my personal macbook and it all seemed to go
fine. (Somehow I got ant on this machine and I don't remember installing
it, does it come with xcode?)
As for the node dependency it looks like the packager bundles node with it (
I put together a small prototype so people can see what the user feel would
be like:
https://github.com/gtanner/incubator-cordova-blackberry-webworks/tree/blackberry.ndk
This currently only works and has been tested on OSX (sorry Jesse :P) but I
will add windows support of this idea takes off.
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
Making sure I understand the steps:
1. User downloads and installs BlackBerry 10 Native SDK and Cordova.
2. Executing the create script to create a project will somehow determine
if the user has the WebWorks SDK and if not...
3. Clone the WebWorks SDK using git.
4. Build the WebWorks SDK.
5.
If clone off the WebWorks repo and then checkout a tag for the last release
it will be the same as the last release.
It should not be prone to any errors.
On Wed, Dec 5, 2012 at 2:53 PM, Drew Walters deedu...@gmail.com wrote:
Making sure I understand the steps:
1. User downloads and installs
Correct. This would be for any cordova BlackBerry 10 APIs (not external
plugins).
This will allow us the native compile step for Cordova that we don't have
access to with WebWorks (that other platforms have).
The key for this is flexibility. Nothing is changing with this now but
allows us more
I think it's worth investigating and having a working prototype but would
caution against immediately merging in until different folk have had a
chance to play with it and make sure our end-user dev experience is cool.
On 12/5/12 12:02 PM, Gord Tanner gtan...@gmail.com wrote:
Correct. This would
+1
I want this to go over more than a Works on my machine test before I land
this in master.
On Wed, Dec 5, 2012 at 3:11 PM, Filip Maj f...@adobe.com wrote:
I think it's worth investigating and having a working prototype but would
caution against immediately merging in until different folk
So, if the WebWorks SDK itself needs to provide native code for
functionality, how will that be provided?
What dependency differences are we looking at? Looks like to pull and
build WebWorks SDK it would require git, node, npm, native SDK. Anything
else? Does the native SDK have any pre-reqs?
Please remember Windows users in your decision making.
Not sure if it makes a difference, but how cross platform is the
suggested solution?
On Wed, Dec 5, 2012 at 12:30 PM, Drew Walters deedu...@gmail.com wrote:
So, if the WebWorks SDK itself needs to provide native code for
functionality, how
WebWorks SDK builds are cross platform and use node. Works on windows, mac
and linux
We try to be a responsible open source project and allow building on all
platforms, as many of our developers are on Windows as well. We have had
some issues about windows in the past but obviously given enough
Is dependencies on node and npm a problem?
I was thinking this wouldn't be that big of a problem since Cordova-client
depends on those projects too.
If it is a huge deal I can look into removing those dependencies
Sent from my iPhone
On 2012-12-05, at 3:30 PM, Drew Walters deedu...@gmail.com
I don¹t think a dependency on node/npm is any more problematic than a
dependency on ANT, for example.
On 12/5/12 2:55 PM, Gord Tanner gtan...@gmail.com wrote:
Is dependencies on node and npm a problem?
I was thinking this wouldn't be that big of a problem since
Cordova-client depends on those
Just to be clear, I wasn't complaining about node/npm dependencies, was
just curious what full dependencies would be.
On Wed, Dec 5, 2012 at 4:59 PM, Filip Maj f...@adobe.com wrote:
I don¹t think a dependency on node/npm is any more problematic than a
dependency on ANT, for example.
On
14 matches
Mail list logo
