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
The usage of Sprotty in our project requires to create static SVG screenshots from the graphs rendered with Sprotty. As an additional requirement this needs to be done headless (with node.js only?) and fully self-contained SVGs (on CSS referenced or inlined - all styles need to be part of the corresponding SVG elements).
The text was updated successfully, but these errors were encountered:
@spoenemann Please analyse the need to render the hidden model again in case of SVG export. In general an analysis of the performance would be good. Where is time spent on SVG export compared to normal rendering (e.g. embedding CSS styles, size calculation, ...)
The usage of Sprotty in our project requires to create static SVG screenshots from the graphs rendered with Sprotty. As an additional requirement this needs to be done headless (with node.js only?) and fully self-contained SVGs (on CSS referenced or inlined - all styles need to be part of the corresponding SVG elements).
The text was updated successfully, but these errors were encountered: