> For web and embedded I would still need to dynamically control transforms of object groups. Looking at what people mostly use SVG's for on the web, most peop

> For web and embedded I would still need to dynamically control transforms of object groups. Looking at what people mostly use SVG's for on the web, most people don't agree with you. Like I said most SVG's I see are either static icons, diagrams or graphs. Weather it would be better for them to be bitmaps is another discussion. Lately in embedded I often come in situation where I have CPU cycles to spare, but bump into available storage limit on micro. So this might make sense in such situation Whole point of this format is to be 80%. that's why it has tiny in name :) If you want to do dynamic content this is not format for you. > Otherwise the graphics is baked and I can just as well use PNG. that's what I use now. But I will try this TinyVG for my next projects dashboard icons, to see cpu/storage space is favorable