understand how all this translation and scaling and clipping works with all these abstractions. If inkview could provide more simple output to see how it works, it could become a part of coordinate tutorial itself.
I think that deserves a separate thread out of `inkview` and Python bindings context, because I forgot to stress that using SVG is a kind of mess, because of those endless coordinates - everything tends to grow of shrink or seems too detailed and overburden the CPU while painting. Having some sane anchor to streamline SVG works with instruments that `inkview` can become that give necessary details about the CPU cycles being used, about details that are missing at the viewing resolution and hints how to optimize glyphs to make processing more simple, and how coordinates are mapped, how to avoid scaling, and simple buttons (or mode with buttons) to optimize for those inefficiencies - that would help people build their SVG composition pipelines for daily small graphics works.