... | ... | @@ -22,7 +22,30 @@ this.popOver_warnings.hide(); |
|
|
GuiSvgPlott.getInstance().closeWizard(true);
|
|
|
```
|
|
|
|
|
|
The `guiSvgOptions` variable holds an instance of `SvgOptionsService` which is GuiSvgPlots own model class holding all data and properties of the chart. Essentially it wraps an instance of `SvgPlotOptions`, which comes directly from the `tud.tangram.svgplot.options` package.
|
|
|
The `guiSvgOptions` variable holds an instance of `GuiSvgOptions` which is GuiSvgPlots own model class holding all data and properties of the chart. Essentially it wraps an instance of `SvgPlotOptions`, which comes directly from the `tud.tangram.svgplot.options` package.
|
|
|
|
|
|
This data which was accumulated during the plot creation process in the graphical user interface is then passed to the `buildSvg()` method of the `SvgOptionsService`, which is a controller class doing the invokation of SvgPlot.
|
|
|
|
|
|
### Extending the current approach
|
|
|
|
|
|
A minor problem which presents itself at this point is, that the integration of the brailleplot integration cannot simply happen by adding it as a normal output device option, just as the other options (Standard, TigerEmbosser, Screen, PinDevice, ...), since these are just options handed over to SvgPlot, which then essentially treats them as different modes of operation.
|
|
|
|
|
|
Our brailleplot application however is completely indepented from SvgPlot and rather serves as alternative plot generation process. So it will be necessary to extend the GuiSvgPlot structure to portray this relation.
|
|
|
|
|
|
This will be done by extending the current `SvgOptionsService` controller with a method `buildBraillePlot()` and deciding which of both methods to use based on the selected output device in the `GuiSvgOptions` container.
|
|
|
|
|
|
The limitations of the braille plot usecase however will also limit the available options significantly, when brailleplot is used as output device. Only a subset of the defined options can be passed to the application. This limitation of the controller must of course be represented in the view. The resulting changes which were made to the GUI to achieve this are discussed in another section: GUI changes
|
|
|
|
|
|
### Invokation of the brailleplot application
|
|
|
|
|
|
As discussed before, the `SvgOptionsService` controller class will be equipped with an additional method for brailleplot creation. This is the code used for this purpose:
|
|
|
|
|
|
```
|
|
|
no
|
|
|
code
|
|
|
here
|
|
|
```
|
|
|
|
|
|
### GUI changes
|
|
|
|
|
|
... |
|
|
\ No newline at end of file |