Make async waiter explicit MojoGLES2CreateContext param
commit882aa3c950a867ce5485cd2a505d3fd194532714
authorjamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 12 Aug 2014 21:52:41 +0000 (12 21:52 +0000)
committerjamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 12 Aug 2014 21:54:19 +0000 (12 21:54 +0000)
treea432a6d954c450dfeac13f845aa66c37a3196fe6
parent15b9275f70a35750c5bb3bf38dc69b72f83b55aa
Make async waiter explicit MojoGLES2CreateContext param

Hiding the async_waiter in a static makes it difficult to deal with
different threads running potentially different loop types running in
the same process. Making this explicit in the create call is much easier.
This assumes that callers will want to permantently bind a context with
a particular async waiter. In the case that we end up with a caller that
wishes to create a context on a thread using one async waiter type and
then bind that context to a thread using a different async waiter type
we can add another version of MakeCurrent, but that seems like a fairly
remote possibility at this point.

R=piman@chromium.org

Review URL: https://codereview.chromium.org/428413002

Cr-Commit-Position: refs/heads/master@{#289074}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289074 0039d316-1c4b-4281-b951-d872f2087c98
16 files changed:
mojo/apps/js/bindings/gl/context.cc
mojo/apps/js/main.cc
mojo/cc/context_provider_mojo.cc
mojo/examples/compositor_app/compositor_app.cc
mojo/examples/pepper_container_app/graphics_3d_resource.cc
mojo/examples/pepper_container_app/pepper_container_app.cc
mojo/examples/sample_app/gles2_client_impl.cc
mojo/examples/sample_app/sample_app.cc
mojo/gles2/gles2_impl.cc
mojo/mojo_examples.gypi
mojo/public/c/gles2/gles2.h
mojo/public/cpp/gles2/gles2.h [deleted file]
mojo/public/platform/native/gles2_thunks.cc
mojo/public/platform/native/gles2_thunks.h
mojo/services/surfaces/surfaces_impl.cc
mojo/services/view_manager/root_view_manager.h