You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Plots in the SmaRP app are currently fixed to 800px width, which makes them only partially visible in smaller browser windows / screens. There is also no horizontal scroll bar on the page.
The approach here is to make sure the plot width does exceed the column size, and the height is adjusted accordingly. This can be achieved with CSS as follows:
set a max-width: 100% property
adjust the height depending on the @media size (keeping the aspect ratio is tricky and would require some JavaScript)
Note that resizing the window will not re-render the googleVis plots, so the effect of resizing this will be seen upon a change to the inputs causing a re-rendering of the plots.
As part of this, the legend labels should be written using spaces instead of underscore _, similar to what done in the Report (#82)
The text was updated successfully, but these errors were encountered:
* Dynamic plot size via CSS `max-width: 100%` and `@media`-dependent height, and using relative gvis `chartArea`.
* More meaningful plot IDs.
* Use spaces and no `_` for the labels.
Plots in the SmaRP app are currently fixed to 800px width, which makes them only partially visible in smaller browser windows / screens. There is also no horizontal scroll bar on the page.
The approach here is to make sure the plot width does exceed the column size, and the height is adjusted accordingly. This can be achieved with CSS as follows:
max-width: 100%
property@media
size (keeping the aspect ratio is tricky and would require some JavaScript)Note that resizing the window will not re-render the googleVis plots, so the effect of resizing this will be seen upon a change to the inputs causing a re-rendering of the plots.
As part of this, the legend labels should be written using spaces instead of underscore
_
, similar to what done in the Report (#82)The text was updated successfully, but these errors were encountered: