11-30-2013 01:31 PM
any help on this ? The website doesn't seem to let me download the webworks sdk 2.0.
I keep clicking the link to get the sdk and instead of downloading the dmg file (running mac), it keeps redirecting me to the same page.
does the download work for anyone else ?
12-02-2013 02:27 PM
Any recommendations you have, or issues you encounter, please submit them through the issue tracker. The WebWorks team is eager to make the WebWorks 2.0 experience excellent in time for the Gold release, and that's the best way for us to capture all the details of what you are suggesting or seeing.
12-02-2013 05:21 PM
Yes i have the following:
and looking at the console window i have the same 404 errors.
If i open the Console tab in the browser tools, i have:
seems to be made within jquery file.
12-03-2013 03:19 PM - edited 12-03-2013 03:20 PM
Just a note on this - I'm on Windows 7, and I just installed the SDK, and put it into my D drive (for organization). Anyways, turns out that HOMEPATH returns "/users/ME", and USERPROFILE returns "c:/users/ME". So, since HOMEPATH is higher precedence in the findHomePath function in utils.js, and the SDK is installed on my other drive, I was getting a home path of d:/users/ME which doesn't exist obviously. This reared its head when I tried to create a new directory (couldn't get to the .cordova directory).
In addition, I know this is beta, but, my dialog is never actually closed when the create fails (either for the above issue, OR when my project folder already existed) - I gather this is because the error callback is never actually passed in on the server.create function.
EDIT: And, just realized I should put this in the issue tracker :-)
12-04-2013 09:00 AM
Its relatively easy to hack it - under the webworks SDK directory, go to webworks-cli/lib/utils.
Edit the utils.js file and change the findHomePath function to be:
return process.env.HOME || process.env.USERPROFILE || process.env.HOMEPATH;
12-04-2013 04:27 PM
Sorry for the delay, the issue tracker is here: https://www.blackberry.com/jira/secure/Dashboard.j
Use your BBID to login.
You're pointing out some great insights so this would be really excellent to capture there.