Changed resizer to divide device pixels by css pixel ratio when formatting the iframe.  changed affected devices
Array.push throwing TypeError                     TypeError: Array.prototype.push called on null or undefined
`test/unit/webworks` needs to be split up appropriately.

This is because we started with one folder, then later on, we started
coding modules for tablet specific implementations, and thus core,
handset and tablet folders were created.

There is stll some overlap in the `webworks.core` specs, as some test
handset/tablet specific stuff (ex spec.objects structure), however, for
the most part, they are now split up to the point where the `webworks`
folder no longer exists.

GitHub Issue:
https://github.com/blackberry/Ripple-UI/issues/294
There is no Acer A500 device.
Accelerometer tests were failing do to timestamp race conditon.

At times, the timestamp would be 1ms (or greater) off, and it would
cause the test to fail "randomly".

There was also a duplicate, which was removed.
`utils.rippleLocation()` returns wrong value if path has "." in it.

GitHub Issue:
https://github.com/blackberry/Ripple-UI/issues/315
Merge branch 'master' into next
Merge branch 'task-apply.css.pixel.ratio.to.iframe' into next
Merge branch 'next' of github.com:tinyhippos/Ripple-UI into next
fixes issue #572
merged task-correct.ppi.numbers
Updated two torch models (9810 and 9850/60) PPI numbers per RIM specs at http://ca.blackberry.com/smartphones/blackberry-torch-9800-9810.html#/h:/smartphones/blackberry-torch-9800-9810/phone-specifications.html and http://ca.blackberry.com/smartphones/blackberry-torch-9850-9860.html#/h:/smartphones/blackberry-torch-9850-9860/phone-specifications.html
Cross origin (HTTPS) XHR calls should use SSL between client & server.

Note: This is only when using the cloud based server, and not a local
instance of Ripple's API server.

There was a recent update that got deployed to rippleapi.heroku.com that
adds support for using SSL (in a fashion). Given that, whenever a user
makes a cross origin XHR call, the client (i.e. Ripple's UI) can always
use HTTPS when calling out to Heroku, as you can "piggyback" off their
SSL certs. This also meant the URL needed to be changed to a non mapped
domain name.
updated updates.xml to include the correct path to the crx as it changed with the micro site refresh
fixed don't panic screen showing up when in file:/// scheme
The browser test runner was not passing all tests.

This was due to a lazy regex match that threw an exception when the
`<body>` tag was modified to have an extra attribute on it.
There need only be one jWorkflow file used in the project.

Some time ago, the npm package of jWorkflow was used (for ease) in the
node (unit) test runner, while the one in `thirdparty/jWorkflow` was
being used in Ripple proper, and in the browser runner.

The npm package is now the sole location of jWorkflow in the project,
and the `thirdparty/jWorkflow` (submodule) folder has been removed.
The node-XHR lib has an NPM package.

Using NPM packages vs a git submodule for this is better because it is
more consitent with the rest of the thirdparty dependencies we use, and
it also plays a lot nicer in general, considering dev workflow.

This will now get installed via `npm install` (in `configure`).
Added support for blackberry.invoke.card.invokeCamera

- unit tests and functional code for card
- updated the camera ui plugin to allow taking videos and audio
- took out running of systemEven integration tests as they seem to fail
  for unknown reasons on random machines.
- removed the bin def from package.json as it was causing issues with
  ./configure since we simlink into node_modules now
fixed webworksready event firigin multiple times when iframe was refreshed. fixes issue #486