End-users may wish to have some control over the display of the diagrams, such as flipping all on a page to left-handed diagrams (see #5). This should be exposed via an optional page configuration block with buttons.
Acceptance Criteria
[ ] A mechanism to enable global (page-level) configuration options exists
[ ] ...with configurations for which options are available
...that could include:
[ ] Scaling (#4)
[ ] Mirroring (#5)
[ ] Colors/contrast ❓
[ ] Others ❓
Approach
Consider how the canvas is rendered via JS function and use that for specifying there the global controls should be assigned
Does this require a higher-level or global diagram object to store all the diagrams on a page? That is, instead of this:
let gdj1 = new GuitarDiagramsJS();
let gdj2 = new GuitarDiagramsJS();
...should it be more like this?
let gdj = new GuitarDiagramsJS();
let gdj1 = gdj.newDiagram();
let gdj2 = gdj.newDiagram();
Better idea: make a GuitarDiargramsCollection object and add gdj objects to it, then have that object render the controls. This avoids the extra layer of overhead when users don't want the global options.
Background
End-users may wish to have some control over the display of the diagrams, such as flipping all on a page to left-handed diagrams (see #5). This should be exposed via an optional page configuration block with buttons.
Acceptance Criteria
Approach
...should it be more like this?
Notes
TBD