This is a fabulously educational topic!
Thanks all, I’ve learnt quite a bit and would now like to try SVGs…
disclaimer Ive never bothered until now, but this is great, I now have WAY more understanding of the concepts employed and how it actually works and with regards the whole Caching thing… that’s interesting!
SO, from all the actually techie side of things, it looks like @AllMediaLab 's idea kind of wins on points, after, reading the linked content etc.
However, from the User experience point of view, ie, being a numpty , who forgets everythign, like myself, then the whole PG UI way of doing it sounds fabulous!..providing I have no clue about the data overheads and speed implications that @AllMediaLab mentions…
So, I get you both and both seem to have merit, but if I was smarter, and used them a lot… and cared about performance, It looks like Id have to end up going doing the @AllMediaLab route, gnashing my teeth and cutting and pasting, into separate files etc, but sounds like I would then also loose the PG UI sweetness.
But, in the end, the PG UI sweetness… doesn’t count for much, once the site is deployed to my server…er, which very few of them are!
SO its like the PG approach to it is fab, and all bells and whistles and flexibility,
And the @AllMediaLab approach, is entirely data economy and overhead driven.
Could you have a tick box option to cater for the later (probably with a load of hassle?
save to external svg
move inline svg to external file etc etc, AFTER creating/editing?
oh! LOL @AllMediaLab just wrote the same as my conclusion, as I was writing it!