Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(557)

Side by Side Diff: mojo/public/c/README.md

Issue 2009893002: Mojo bindings: remove an outdated TODO. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 Mojo Public C API 1 Mojo Public C API
2 ================= 2 =================
3 3
4 This directory contains C language bindings for the Mojo Public API. 4 This directory contains C language bindings for the Mojo Public API.
5 5
6 GLES2
7 -----
8
9 TODO(yzshen): move GLES2 to where it belongs (likely components/mus).
10
11 The gles2/ subdirectory defines the GLES2 C API that's available to Mojo
12 applications. To use GLES2, Mojo applications must link against a dynamic
13 library (the exact mechanism being platform-dependent) and use the header files
14 in this directory as well as the standard Khronos GLES2 header files.
15
16 The reason for this, rather than providing GLES2 using the standard Mojo IPC
17 mechanism, is performance: The protocol (and transport mechanisms) used to
18 communicate with the Mojo GLES2 service is not stable nor "public" (mainly for
19 performance reasons), and using the dynamic library shields the application from
20 changes to the underlying system.
21
22 System 6 System
23 ------ 7 ------
24 8
25 The system/ subdirectory provides definitions of the basic low-level API used by 9 The system/ subdirectory provides definitions of the basic low-level API used by
26 all Mojo applications (whether directly or indirectly). These consist primarily 10 all Mojo applications (whether directly or indirectly). These consist primarily
27 of the IPC primitives used to communicate with Mojo services. 11 of the IPC primitives used to communicate with Mojo services.
28 12
29 Though the message protocol is stable, the implementation of the transport is 13 Though the message protocol is stable, the implementation of the transport is
30 not, and access to the IPC mechanisms must be via the primitives defined in this 14 not, and access to the IPC mechanisms must be via the primitives defined in this
31 directory. 15 directory.
32 16
33 Test Support 17 Test Support
34 ------------ 18 ------------
35 19
36 This directory contains a C API for running tests. This API is only available 20 This directory contains a C API for running tests. This API is only available
37 under special, specific test conditions. It is not meant for general use by Mojo 21 under special, specific test conditions. It is not meant for general use by Mojo
38 applications. 22 applications.
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698