Add myself to the AUTHORS file.
[XESh] Move all v8 related code to V8Runner.

This commit moves every v8 related code to V8Runner.
XWalkExtensionClient was also moved to XEShV8Runner because it
relates to a v8::Context (through XWalkModuleSystem). That cleans
up xesh_main.cc (hence, ExtensionManager), leaving
there only native-related pieces of the Extensions Framework.
[XESh] Move V8Runner to its own thread.

This patch fixes XESh so it can handle sync messages.
After some investigation we realized this bug was being
caused due to both native extensions code and their
JavaScript context being kept in the same thread.

BUG=https://crosswalk-project.org/jira/browse/XWALK-304
TEST=./xwalk/extensions/xesh/xesh_test.sh ./out/Release/
[Android] Add "--tool-path" option for make_apk_test.

Because the xwalk_app_template target will be moved out of the "out" folder
on buildbot/trybot when the feature of generating separate APK for ARM and x86 arch
is ready. So add more flexible option "--tool-path" to replace the "--build-dir"
and "--target" options for the make_apk_test.py.
[Android] Enable W3C fullscreen API support

Fullscreen API spec is at http://www.w3.org/TR/fullscreen/.
The API allows web app to switch between fullscreen/non-fullscreen
dynamically in javascript. And also the ability to fullscreen a
dom element.

For Android, Content already provide related interface in WebContentsDelegate.
Implementing the interface and bridge to XWalkWebChromeClient finally to
toggle Activity's fullscreen status.

TEST=Manual
BUG=https://crosswalk-project.org/jira/browse/XWALK-773
[Android] Implement the functions of application working from SD-Card.

  Crosswalk for Android port doesn't support the functions of application
moving to SD-card and working from SD-Card. This is because the AndroidManifest.xml
in xwalk app template doesn't support the application installation settings for
"preferExternal" or "Auto", and the corresponding intent actions should be registered
as response to the mounting and unmounting of SD-Card. This feature is to enable
the SD-Card related function supports.

BUG=https://crosswalk-project.org/jira/browse/XWALK-774
DEPS.xwalk: Track ozone-wayland.git.

This is a very important part of the process, as the code expects ozone/ to
be in src/.
Ozone: do not call Widget::CenterWindow() when initializing the view.

If that is not done, Crosswalk's window will be 1x1 in size inside Weston.
[SysApps] Simplification of how to init the PathServices

As suggested by Babu, there is a much easier way to start the
PathService specifically for testing.
Merge pull request #1457 from tmpsantos/media_init

[SysApps] Simplification of how to init the PathServices
Merge pull request #1455 from rakuco/ozone-wayland

Add support for Wayland to Crosswalk.
[Packaging] Pass --no-keep-memory to ld by default.

When building Crosswalk (Chromium, in fact) on an IVI chroot, ld ends up
running out of memory.

Work around the issue by passing --no-keep-memory to ld so that it optimizes
for memory consumption over speed. I have not noticed any significant drop
in speed, though.

Do not add any checks for IVI as it does not hurt to have this on all
profiles.
[Packaging] Be compatible with multiple Tizen versions and profiles.

Prepare for the future and start detecting features and versions so that we
can support other Tizen versions and profiles besides Tizen 2.1 Mobile.

Checking for specific profiles is not very future-proof. We therefore try to
look for either specific features that may be enabled in the current profile
(such as Wayland support) or for a certain Tizen major version (the
differences betwen Tizen 2 and Tizen 3 are big enough that we need different
patches and build dependencies, for example).
[Packaging] Add a Mesa patch for Wayland when building for Tizen.

Import a patch from the Ozone-Wayland repository to prevent crashes when
using Mesa and Ozone caused by the way Chromium has GL headers in both
third_party/khronos and third_party/mesa and the wrong ones (with wrong
pointer sizes) may be picked up.

This patch should actually be used by anyone testing Chromium on Wayland,
but this would require us to have a Chromium Mesa fork of our own. For now,
then, we're going to apply it automatically only for Tizen and try to solve
the issue upstream. It is tracked by http://crbug.com/266310
Merge pull request #1459 from rakuco/tizen-ivi-support

[Packaging] Add all necessary spec file changes to support Tizen IVI.
Bump version to 4.32.68.0
[Android] Fix the crash issue of loading app from app:// scheme.

The fixed places:
1. As the resource rquest URL was canonicalized to lowercase in
runtime core, the host name exacted from the URL may be inconsitent
with the app package name, if there is capital letter in the package
name. So convert package name to lowercase before comparing these
two strings.
2. The unpermitted resource request should not be processed. Once
such request is received, the request job should be marked as done,
and should returned from the process function at once. So add the
missing return to the related place.

BUG=https://crosswalk-project.org/jira/browse/XWALK-808
Merge pull request #1458 from gaochun/bug808

[Android] Fix the crash issue of loading app from app:// scheme
Merge pull request #1444 from junmin-zhu/toolpath

[Android] Add "--tool-path" option for make_apk_test.
Merge pull request #1398 from zhang-qing/master

Add myself to the AUTHORS file.