gosuwachu/SVGKit — comment on commit b4b96c1e8e188838fababd5cd5ed25b8ed523135
File:  line 0
By adamgit:

Sounds a nice idea. Could you make it optional, instead of forcing it this way? I've already split the "parsing from disk" and "render to screen" into two separate chunks - the idea is that you could implement something like this by providing an alternative renderer - without overwriting the existing one.

e.g. look at how SVGDocumentView is used - that's the primary renderer at the moment. You could easily generate an alternative that plugged-in to SVGDocument in the same way, but output a single CALayer, I think?

Lots of people require the rendering in multiple CALayer's (for instance, we use it a lot in game development - it's a great way of storing an entire "level" of movable and non-movable items). It's a great feature of SVG that you get a layered hierarchy of rendered objects, that you can easily move around at runtime.