[WiDi API] Add the OWNERS file for Presentation API
[Android] Testcase for Presentation API:displayavailable
1: Add testcase for both shared and embedded mode.
2: Add call onResume() after onCreate() in setUp() method.
   PresentationExtension need to do some init work in this life cycle method
[Tizen] Enabling Hardware Acceleration with Libva and EGL in
    VDA for Tizen Mobile within chromium v31+. [standalone packaging]

Why we need to maintain it in our side:
===========================================
1) Upstream confirm VAVDA will continue to be restricted to
   CrOS/X86 for dev & testing only and not for chromium road map.
2) CrOS/X86 no plan to expend EGL backend which finalize in
   June 2012 and be addressed to the CrOS graphics team.

So, the upstream no plan to lerage VAVDA with EGL graphic
   backend for any X86.

3) The tizen-mobile's driver only support EGL as texture
   backend. The video hw acceleration of xwalk have to
   rely on EGL not GLX to bind decoded pixmap.
===========================================
That's why we enable specific EGL for VAVDA in tizen port.
Merge pull request #1063 from kurli/presentation_test

[Android] Testcase for Presentation API:displayavailable
Merge pull request #892 from zhang-qing/master

[Tizen] Fix: issue#891 Enabling video hardware acceleration with Libva and EGL.
Adding sysapps/OWNERS file
Adding tizen/OWNERS file
Merge pull request #1097 from cmarcelo/sysapps-owners

Adding sysapps/OWNERS file
Merge pull request #1098 from cmarcelo/tizen-owners

Adding tizen/OWNERS file
Merge pull request #1078 from hmin/owner

[WiDi API] Add the OWNERS file for Presentation API
[XESh] Print both Crosswalk and v8 version

This patch adds a PrintInitialInfo() function that
prints Crosswalk and v8 versions, in addition to the
XESh "banner".

After that there is no need to keep the JS version();
callback implemented, so it was removed from V8Runner.
[UI][Tizen] Create NativeAppWindowTizen

Instead of adding custom behavior into NativeAppWindowViews behind
ifdefs, we create a proper subclass for Tizen. This allow us to
implement observers directly in our window, for example the sensor
observer.

This is a preparation for allowing the window to tell the indicator
which orientation it should paint. In the previous design (using
TizenSensorObserver) we would end up adding more couple (or more layer
of indirection) to accomplish this.

There are some "ifdef" leftovers in NativeAppWindowViews, but can be
moved in later patches.
Merge pull request #1100 from jeez/xesh

[XESh] Print both Crosswalk and v8 version
[Extensions] Reduce boilerplate for external extension tests

Two changes collaborate here to reduce the boilerplate:

- Make a specialized static function to store the external extension
  path for tests, so no reference to a concrete XWalkExtensionService
  is needed.

- Now that we do not need the reference use SetUp() function instead of
  the callback for registering extensions in tests. This change make the
  service passed in that callback unused, we'll remove in the next patch
  to keep this easier to review.

A helper function was added to get the path where an external extension
built for test is.
[Extensions] Remove service parameter from register test callback

XWalkExtensionService allows us to register a function to be called
every time a new XWalkExtensionServer is created, so tests can register
specific extensions. This function may be called multiple times because
we create a (in process) server per Render Process created.

The callback also received a service parameter, to be used for setting
the path for external extensions to be loaded. But the previous commit
changed how tests handle this, so the parameter can be removed.
[Extensions] Add RegisterExtensionForTest() function

This is a small convenience function that reduces the boilerplate when
registering extensions in tests.
[Extensions] Check if reply is valid after a SendSyncMessageToNative

When we try to send a sync message to an extension instance that
became invalid (i.e.: the extension process died) then we might
end up with a NULL reply. We should then check before converting
to a V8Value, thus avoiding the RenderProcess to crash.

That is the same behavior PostMessageCallback has nowadays.
Merge pull request #1101 from cmarcelo/reduce-extension-tests-boilerplate

[Extensions] Reduce extension tests boilerplate
Merge pull request #1102 from cmarcelo/native-app-window-tizen

[UI][Tizen] Create NativeAppWindowTizen
Revert "[UI][Tizen] Create NativeAppWindowTizen"

This reverts commit bd10f497110662662e39e738f91e246d058b5356. It was
still a draft, testing pending.