Update instructions.

Conflicts:
	README.md
Add xwalk path to git ignore list
Also need to set aura::Window title

Since each DesktopNativeWidgetAura uses a sole aura::Window as its
backed, once the title of native widget gets updated, the title of
aura::Window should also be updated in addition to updating the
XWindow created by DesktopRootWindowHostX11.

BUG=https://github.com/otcshare/crosswalk/issues/191
TEST=xwalk_browsertest --gtest_filter=XWalkRuntimeTest.GetWindowTitle
Aura: fix the touch event doesn't work on Tizen 3.0 issue.

Chromium uses the sourceid of a XIDeviceEvent to decide if it is orignated
from a touch device. See events_x.cc:717. However, Chromium uses deviceid to
check touch device. See touch_factory_x11.cc:158.

As X11 spec, only slave device has same sourceid and device id. So Chromium
should setup touch device list with XISlavePointer other than XIMasterPointer
device.

BUG=https://github.com/otcshare/crosswalk/issues/187
TESTS=https://github.com/borismus/MagicTouch/blob/master/samples/tracker.html
Add factory mechanism to DesktopRootWindowHost.

Uses the given DesktopRootWindowHostFactory to override the default
DesktopRootWindowHost implementation for embedder.

After this patch, xwalk maintains DesktopRootWindowHost inside xwalk.
Export DesktopCursorLoaderUpdaterAuraX11 and DesktopFocusRules to maintain DesktopRootWindowHost inside xwalk.

We will perhaps make something like ui/views/widget/desktop_aura inside xwalk to
satisfy our all requirements. At that time, this patch can be rollbacked.
Fix touch support issue on Tizen 2.1

On Tizen 2.1, the multi-touch support is different from the XInput2.2
approach. It extends the older Input2.1 spec to use multiple touch
devices for multiple touch points, one touch device for one touch
points. The device type name for this purpose is MULTITOUCHSCREEN which
is not defined by XInput extension.

This fix is to make Crosswalk be able to handle the new extension to
XInput2.1 by introducing a new build option 'enable_xi21_mt'. It should
be turned on for Tizen 2.1, and is exclusive to 'use_xi2_mt' option.
Polish the comments for enable_xi21_mt usage.
Move ENABLE_XI21_MT definition to xwalk.

We don't want to change chromium sources if possible.
Adapt bindings generators to Crosswalk

Change some paths and names of functions generated to make it
aligned with the conventions used inside Crosswalk. We also disable
the compilation of the function registry because we are not using it.
We have a different way of registering handlers.
Create GPU process object before creating GPU thread in single process

This commit is partly backport upstream commit 57cf9788
When creating GPU thread, it need a ChildProcess singleton object
which is not exist if not creating GPU process object.

In-process mode create ChildProcess object in browser process, it breaks
the assumption that ChildProcess is singleton. So remove the relevant
DCHECKs.

BUG=https://github.com/otcshare/crosswalk/issues/229
Cherry-pick upstream commit 18366f5 (r211568).

This is basically commit 81ee198 in the master_history_28_0_1500_36 branch,
which did not apply to Chromium 29. This commit can be removed once we move
to a more recent Chromium.

Original commit message:
  Allow MultiResolutionImageFetcher to fetch image from file scheme URL

  This fix is to also check the scheme of image url for fetching image from
  file scheme since there is no http status code for file scheme URL.

  BUG=246511
  TEST=Follow the description of http://crbug.com/246511

  Review URL: https://chromiumcodereview.appspot.com/16358002

  git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211568 0039d316-1c4b-4281-b951-d872f2087c98
[Android] Fix a set of rendering issues introduced by single process mode.

* There is browser side compositor in Android port, in single process mode. the
gl contexts in renderer will have race conditions with gl contexts in browser side.

* This issue leads to many rendering failes: (1) stop activity and then restart
will cause black screen; (2) Any page with compositing layers will leads to the
compositing layer black (WebGL. Canvas, Video).

* Fix this issue by duplicating the gl contexts implementation in browser side.

* This is a workaround fix for the critical blocking issue.

BUG=https://github.com/otcshare/crosswalk/issues/449, 430, 447, 455
Fix the issue of video/audio playback with file://android_asset scheme.

The MediaPlayerBridge in Chromium accepts uri as data source, but MediaPlayer
can't handle file:///android_asset. So for such case, handle it specially.
Fix the issue of ContentShell can't play video with file scheme.

MediaInfoLoader checks single security origin and CROS access, but for media
resources with file protocol, it always returns false, which disables local
video playback.

BUG=234710
TEST=video with file protocol

Review URL: https://chromiumcodereview.appspot.com/19324002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211967 0039d316-1c4b-4281-b951-d872f2087c98
Merge pull request #53 from sqliu/otcshare-local-media

[Android] Fix the issue of ContentShell can't play video with file scheme.
Revert "Adapt bindings generators to Crosswalk"

This reverts commit 3b7a5f2da635f47a7c87e03b8e6aa06691307c08.

This patch is no longer needed because we are not using JSON Schema
compilers and bundles. Either way, the patch upstream with a proper
fix to this got a LGTM and should land soon.
Merge pull request #50 from sqliu/otcshare-fix-media-asset

[Android] Fix HTML5 video/audio can't play with file:///android_asset scheme.
Merge pull request #49 from sqliu/otcshare-single-process-ctx

[Android] Fix a set of rendering issues introduced by single process mod...
Merge pull request #54 from tmpsantos/remove_bindings_patch

Revert bindings generators patch