[API] Move down TC example

...to come after telemetry usage example
This commit is contained in:
Victor Woeltjen 2016-09-07 13:25:05 -07:00
parent 1ae3ce57d0
commit a3c3f997cf

30
API.md
View File

@ -203,18 +203,6 @@ openmct.composition(myObject).load().then(function (childObjects) {
});
```
### Synchronizing with the Time Conductor
Views which wish to remain synchronized with the state of Open MCT's
time conductor should utilize
[`openmct.conductor`]{@link module:openmct.TimeConductor}:
```
openmct.conductor.on('bounds', function (newBounds) {
requestTelemetry(newBounds.start, newBounds.end).then(displayTelemetry);
});
```
### Support Common Gestures
Custom views may also want to support common gestures using the
@ -247,6 +235,24 @@ openmct.objects.observe(myDomainObject, "name", function (newName) {
});
```
### Using Telemetry
Very often in Open MCT, you wish to work with telemetry data (for instance,
to display it in a custom visualization.)
### Synchronizing with the Time Conductor
Views which wish to remain synchronized with the state of Open MCT's
time conductor should utilize
[`openmct.conductor`]{@link module:openmct.TimeConductor}:
```
openmct.conductor.on('bounds', function (newBounds) {
requestTelemetry(newBounds.start, newBounds.end).then(displayTelemetry);
});
```
## Plugins
While you can register new features with Open MCT directly, it is generally