diff options
| author | abarth@chromium.org <abarth@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-01 16:44:56 +0000 |
|---|---|---|
| committer | abarth@chromium.org <abarth@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-01 16:44:56 +0000 |
| commit | 29ccd8e9c7a8f16e2174fdcf9f0bafe10a74db98 (patch) | |
| tree | 240a1bd3a04c89291568f495035edf620e8f93a3 /extensions | |
| parent | 32014604025bb5fb9c378d2b8820f03da3681fe4 (diff) | |
| download | chromium_src-29ccd8e9c7a8f16e2174fdcf9f0bafe10a74db98.zip chromium_src-29ccd8e9c7a8f16e2174fdcf9f0bafe10a74db98.tar.gz chromium_src-29ccd8e9c7a8f16e2174fdcf9f0bafe10a74db98.tar.bz2 | |
Make Mojo's NativeViewportAndroid draw a green square
This CL integrates the MojoView with the native_viewport
service. Instead of creating the MojoView on the Java side,
we now create the MojoViewport via the native_viewport service.
This required teaching mojo_shell about the existence of
activities on Android so that the native_viewport service knew
where to create the view. On Windows, the current desktop
appears to be implicit, which is why we haven't needed this
context object in native_viewport until now.
The one aspect of this CL that I'm not super excited about is
the dependency I've introduced from the native_viewport
service to the shell. It seems likely we'll want to move
some more of the concepts in the shell directory lower down
in the dependency graph if/when we want to support other
embedding of the mojo system besides mojo_shell.
R=ben@chromium.org
Review URL: https://codereview.chromium.org/48713009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232411 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'extensions')
0 files changed, 0 insertions, 0 deletions