| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL switches the native_viewport from using raw GL calls to
using an in-process command buffer. I've plumbed the client
interface to the command buffer as far as the
NativeViewportController, but we really ought to plumb it all
the way into the sample_app.
Of course, once the sample_app moves out-of-process, we'll want
to switch to an out-of-process command buffer.
R=ben@chromium.org, jamesr@chromium.org
Review URL: https://codereview.chromium.org/56543002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232669 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
| |
R=ben@chromium.org
TBR=ben@chromium.org
Review URL: https://codereview.chromium.org/54643006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232427 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
| |
TBR=ben@chromium.org
Review URL: https://codereview.chromium.org/56243003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232423 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
This is a platform-specific View (output surface and event sink). We listen for events and other disposition changes and forward them to app code. In this case I just do something ad-hoc (stringify some event metadata and post to our existing sample app). Once we have bindings, we can surface a better API here. I would also like for the app to request the NativeViewportService from the Service Service, and get a separate pipe for that, rather than reusing the one that is passed through MojoMain (which I think is supposed to only be for surfacing the ServiceService).
Anyway WDYT? If we agree on this I can figure out how to wrap the org.chromium.mojo_shell_apk.MojoView in a NativeViewport.
BUG=
R=abarth@chromium.org
Review URL: https://codereview.chromium.org/51373002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232210 0039d316-1c4b-4281-b951-d872f2087c98
|
