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
So in trying to separate code from data for the ruler drawing algorithm (View::createRulerTextPath) I found that using SVG path strings worked quite well.
This means that, in principle, we can have all of our logos as SVG, which I think is generally how it's done now:
it means scaling the UI is not an issue, we don't have to worry about bit crushing
we can share information like palettes using CSS or similar tag systems
embedding the logos in the documentation requires less storage which keeps the size of the PDF down which does seem to effect load times.
I thought I'd pitch this here before spending time on it because it's a fairly major change, especially since converting raster images to vector images is lossy so it takes a bit of artistic flourish.
Cheers,
Robin
The text was updated successfully, but these errors were encountered:
So in trying to separate code from data for the ruler drawing algorithm (
View::createRulerTextPath
) I found that using SVG path strings worked quite well.This means that, in principle, we can have all of our logos as SVG, which I think is generally how it's done now:
I thought I'd pitch this here before spending time on it because it's a fairly major change, especially since converting raster images to vector images is lossy so it takes a bit of artistic flourish.
Cheers,
Robin
The text was updated successfully, but these errors were encountered: