Visual Segments

[ajayyy]

Fix #538

---

Stored as SVGs with animations

While editing, stored as simpler types that are then converted to one svg per segment.

To play at different speeds, the svg must be modified to have all times multipled by the playback speed.

• Implement editor with custom variables (bounds, etc.)
• add method to convert these to an svg using svg.js
• add custom display code for starting/stopping animations and playing at different speeds
• add a filter on the server to only allow whitelisted xml tags
• stop displaying visual segments in the seek bar?

---

SVG tags must be generated manually since svgjs doesn't support them. They can play fine though when imported.

https://stackoverflow.com/a/51615827/1985387

[LoganDark]

This seems like a fine implementation. Clients (such as the extensions) could support whatever SVG things they want to submit to the server. Circles, rectangles, gradients etc. all fair game. Of course the official extension would likely only support basic shapes for submitting, but this looks very nice and future-proof to me.

[erkinalp]

Why did you close the server side ticket? Server change is definitely required to accommodate this remedy type.