There's already a very good binary encoded vector graphics format, which also supports animation among other things --- SWF. The descriptions in this specification actually look somewhat like it.
The original SVG is 96,719 bytes large, while the optimized one is 85,806 bytes large. When converted to TinyVG, the file shrinks to 27,522 bytes. This means we only have 32% size of the optimized source data.
I have a tiger.swf which is 21381 bytes, and since there's another comment here about gzip'ing them, tiger.swf.gz turns out to be only 17296 bytes. In conclusion, I think a subset of SWF, of which much existing rendering code is available, will provide much better efficiency and compatibility than this.
SWF is flash. Vector graphics are just a subset of the format. Any tool claiming to support that format would have to support the rest of the spec, which is overkill for many vector applications.
Even though Adobe owns SWF, they don't support it in Illustrator outside of exporting.
You can always pull a marketing stunt like .webm vs. Matroska if you want to advertise support for a variant of Flash constrained to just the vector parts.
Plenty of existing tools only support a subset of SWF, mainly the vector graphics and animation parts. It's used for UIs in games and various other applications.
Comments
There's already a very good binary encoded vector graphics format, which also supports animation among other things --- SWF. The descriptions in this specification actually look somewhat like it.
The original SVG is 96,719 bytes large, while the optimized one is 85,806 bytes large. When converted to TinyVG, the file shrinks to 27,522 bytes. This means we only have 32% size of the optimized source data.
I have a tiger.swf which is 21381 bytes, and since there's another comment here about gzip'ing them, tiger.swf.gz turns out to be only 17296 bytes. In conclusion, I think a subset of SWF, of which much existing rendering code is available, will provide much better efficiency and compatibility than this.
SWF is flash. Vector graphics are just a subset of the format. Any tool claiming to support that format would have to support the rest of the spec, which is overkill for many vector applications.
Even though Adobe owns SWF, they don't support it in Illustrator outside of exporting.
You can always pull a marketing stunt like .webm vs. Matroska if you want to advertise support for a variant of Flash constrained to just the vector parts.
Plenty of existing tools only support a subset of SWF, mainly the vector graphics and animation parts. It's used for UIs in games and various other applications.
https://en.wikipedia.org/wiki/Gameswf
Is there a spec for SWF?
https://open-flash.github.io/mirrors/swf-spec-19.pdf