[SystemInfo] Get correct version strings for getCapabilities()
[SystemInfo] Get device capability values for getCapabilities()
[download] Fix JS coding style

Fixes #159.
Merge pull request #183 from deqing/fix-coding-style

[download] Fix JS coding style
Merge pull request #174 from fyraimar/master

[SystemInfo] Fix getCapabilities()
[Time] Only use vconf in mobile
Merge pull request #184 from cmarcelo/fix-build-time

[Time] Only use vconf in mobile
[Time] Fix JS style
[Time] Throw if constructor not called as constructor
[Time] Use std::unique_ptr instead of std::auto_ptr
Merge pull request #185 from cmarcelo/time-small-fixes

Time small fixes
[NetworkBearer] Fix JS style

Fixes #160.
[SystemSetting] Fix JS style

Fixes #164.
[SystemInfo] Small fix to initialization order
Merge pull request #187 from cmarcelo/tec-gardening

Trivial gardening of our code to close issues
[Bookmark] Add stubs for extension native code

Note that we had to depend on evas since favorites.h from
capi-web-favorites does include Evas.h, and its pc file doesn't
explicitly include evas.

EvasObject type is used for manipulating the favicons.
[Bookmark] Implement JS API on top of a fake provider

This patch adds a complete JS API, including all the error handling
covered by TCT tests. The public API is implemented in terms of a
BookmarkProvider object.

At the moment there's a FakeBookmarkProvider implemented, that stores
all the data in JavaScript. This was used to bootstrap the JS API and
implement the error handling. As the name implies, it doesn't actually
store the bookmarks in the real database.

Next step is to replace 'FakeBookmarkProvider' with a real provider
object that communicates with the native side of the extension.
bluetooth: Add BluetoothSocket.readData()

This will only return valid data if called during onmessage() callback.
bluetooth: Add support for BluetoothSocket.onclose() callback

This function will be called when the socket is closed.
bluetooth: Add support for BluetoothSocket.writeData()

writeData() is implemented using a "sync" message, because we need
to reply to the caller the number of bytes written.