ExternalVendorCode/openmct
1
0
Fork 0
mirror of https://github.com/nasa/openmct.git synced 2025-06-16 14:18:16 +00:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

[Documentation] Switch Step 2 to fenced

Browse Source
This commit is contained in:
Alex M
2016-08-24 22:56:43 +03:00
parent 5161205a06
commit 2cb636b050
1 changed files with 167 additions and 161 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/src/tutorials/index.md
View File

@ -2488,6 +2488,7 @@ server. Our first step will be to add a service that will handle interactions
with the server; this will not be used by Open MCT directly, but will be
used by subsequent components we add.
```diff
/*global define,WebSocket*/
define(
@ -2525,6 +2526,7 @@ used by subsequent components we add.
return ExampleTelemetryServerAdapter;
}
);
```
__tutorials/telemetry/src/ExampleTelemetryServerAdapter.js__
When created, this service initiates a connection to the server, and begins
@ -2541,6 +2543,7 @@ subsystems. This means that we need to convert the data from the dictionary
into domain object models, and expose these to Open MCT via a
`modelService`.
```diff
/*global define*/
define(
@ -2621,6 +2624,7 @@ into domain object models, and expose these to Open MCT via a
return ExampleTelemetryModelProvider;
}
);
```
__tutorials/telemetry/src/ExampleTelemetryModelProvider.js__
This script implements a `provider` for `modelService`; the `modelService` is a
@ -2673,6 +2677,7 @@ This allows our telemetry dictionary to be expressed as domain object models
fix this, we will need another script which will add these subsystems to the
root-level object we added in Step 1.
```diff
/*global define*/
define(
@ -2722,6 +2727,7 @@ root-level object we added in Step 1.
return ExampleTelemetryInitializer;
}
);
```
__tutorials/telemetry/src/ExampleTelemetryInitializer.js__
At the conclusion of Step 1, the top-level My Spacecraft object was empty. This