[Messageport] Add Messageport implementation.
authorLeandro Pereira <leandro.pereira@intel.com>
Tue, 29 Oct 2013 19:35:05 +0000 (17:35 -0200)
committerLeandro Pereira <leandro.pereira@intel.com>
Tue, 5 Nov 2013 20:53:11 +0000 (18:53 -0200)
commitda6ee6ec1820d34103fc951431aaa44113c73e77
treee8ffaf75a53b58700af554965a9f2f4c6cc107b9
parent964d0667ec50ccfc2bc4d1ae16f6a9e1be6ce68a
[Messageport] Add Messageport implementation.

Tests are passing, but since application installation support isn't ready,
it requires a few hacks for this to actually work.

This includes writing a short wrapper program that correctly passes the path
to Tizen extensions, adding a mocked version of
`tizen.application.getCurrentApplication()` that returns the standard
`tct-messageport` package ID, installing this package, and modifying
`channel-service` so that the application ID is hardcoded.
messageport/messageport.gyp [new file with mode: 0644]
messageport/messageport_api.js [new file with mode: 0644]
messageport/messageport_extension.cc [new file with mode: 0644]
messageport/messageport_extension.h [new file with mode: 0644]
messageport/messageport_instance.cc [new file with mode: 0644]
messageport/messageport_instance.h [new file with mode: 0644]
packaging/tizen-extensions-crosswalk.spec
tizen-wrt.gyp