Home
last modified time | relevance | path

Searched refs:Mojom (Results 1 – 11 of 11) sorted by relevance

/external/libchrome/mojo/public/tools/bindings/pylib/mojom_tests/parse/
Dparser_unittest.py40 expected = ast.Mojom(
50 expected = ast.Mojom(
142 expected = ast.Mojom(
162 expected = ast.Mojom(
184 expected = ast.Mojom(
344 expected = ast.Mojom(
406 expected = ast.Mojom(
452 expected = ast.Mojom(
543 expected = ast.Mojom(
566 expected = ast.Mojom(
[all …]
Dtranslate_unittest.py49 tree = ast.Mojom(
/external/libchrome/mojo/public/tools/bindings/
DREADME.md1 # Mojom IDL and Bindings Generator
8 Mojom is the IDL for Mojo bindings interfaces. Given a `.mojom` file, the
14 For a trivial example consider the following hypothetical Mojom file we write to
26 [module](#Modules) named `widget.mojom` (and thus fully qualified in Mojom as
28 definitions may be included in a single Mojom file.
60 representing the Mojom contents within the target language. For more details
64 ## Mojom Syntax
66 Mojom IDL allows developers to define **structs**, **unions**, **interfaces**,
71 Mojom files may **import** other Mojom files in order to reference their
75 Mojom supports a few basic data types which may be composed into structs or used
[all …]
/external/libchrome/mojo/public/cpp/bindings/
DREADME.md11 [Mojom IDL and bindings generator](/mojo/public/tools/bindings/README.md), users
24 When a Mojom IDL file is processed by the bindings generator, C++ code is
26 `.mojom` file. Suppose we create the following Mojom file at
85 This document covers the different kinds of definitions generated by Mojom IDL
97 Mojom IDL interfaces are translated to corresponding C++ (pure virtual) class
294 Some Mojom interface methods expect a response. Suppose we modify our `Logger`
506 [Mojom enums](/mojo/public/tools/bindings/README.md#Enumeration-Types) translate
508 underlying type. The typename and value names are identical between Mojom and
513 For example, consider the following Mojom definition:
544 [Mojom structs](mojo/public/tools/bindings/README.md#Structs) can be used to
[all …]
/external/libchrome/mojo/public/js/
DREADME.md11 When a Mojom IDL file is processed by the bindings generator, JavaScript code is
13 we create the following Mojom file at
77 * For each Mojom interface `Foo`, there is a generated `FooPtr` class. It owns
113 `EchoInteger` in the `Echo` Mojom interface, there is a corresponding
139 Some Mojom interface methods expect a response, such as `EchoInteger`. The
191 * For each Mojom interface `Foo`, there is a generated `FooAssociatedPtr` class.
202 By default, generated `.mojom.js` files automatically load Mojom dependencies.
210 For exmple, if at build time the two Mojom files are located at:
273 As a general rule, Mojom definitions follow the C++ formatting style. To make
277 | In Mojom | In generated .mojom.js |
/external/libchrome/mojo/public/interfaces/bindings/tests/
Dversioning_test_client.mojom8 // different versions of Mojom definitions for a fictitious human resource
Dversioning_test_service.mojom8 // different versions of Mojom definitions for a fictitious human resource
/external/libchrome/mojo/public/tools/bindings/pylib/mojom/parse/
Dast.py266 class Mojom(NodeBase): class
273 super(Mojom, self).__init__(**kwargs)
279 return super(Mojom, self).__eq__(other) and \
Dparser.py63 p[0] = ast.Mojom(None, ast.ImportList(), [])
/external/libchrome/mojo/public/tools/bindings/generators/cpp_templates/
Dunion_declaration.tmpl7 // Used to identify Mojom Union Data Classes.
/external/libchrome/mojo/
DREADME.md12 [**Mojom IDL and bindings generator**](/mojo/public/tools/bindings/README.md).
117 ### Mojom IDL and Bindings Generator
119 [**Mojom IDL**](/mojo/public/tools/bindings/README.md), which can be fed to the