Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
Line: 36 to 36 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 62 to 62 | ||||||||
ExtensionRegistry.getInstance().register(CLASSIFICATION, Extension(...)) where CLASSIFICATION is one of (pre-defined): | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
or a new type if you deem it necessary. To keep the code readable, we recommend you to use temporary aliases, which you should clean-up afterwards: | ||||||||
Line: 98 to 98 | ||||||||
where: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
The meaning of arg1 and arg2 varies depending on the classification of the extension.
Perspective Extension | ||||||||
Line: 135 to 135 | ||||||||
If views are using extendable factories, the API of that view should provide sufficient information about how to add factories. Typically views use factories whenever that view needs to react on a user selection, for example a user selects a variable and that view should show something about that variable. In that case the variable selection is coupled to a factory in that specific view such that other contributors can contribute a component for new types of variables. | ||||||||
Changed: | ||||||||
< < | An example is the Outline View. It currently can respond to selections of variables, but it could respond to other types of selections such as tools. For that it has uses factories for which applies: | |||||||
> > | An example is the Outline View. It currently can respond to selections of variables, but it could respond to other types of selections such as tools. For that it uses factories for which applies: | |||||||
|