Tebjan Halm

before drawing `renderer.BeginDraw()` and after `renderer.EndDraw()` in those methods each renderer implementation can do what's necessary. then you can do `svgDoc.Draw(renderer)` and in `Draw` begin and end is called on...

```csharp using (var renderer = new SKSvgRenderer(skSize)) using (var skPictureRecorder = new SKPictureRecorder()) using (var skCanvas = skPictureRecorder.BeginRecording(cullRect)) { renderer.DrawFragment(skCanvas, svgFragment); return skPictureRecorder.EndRecording(); } ``` would become ```csharp //fields SkCanvas...

> ```cs > public interface ISvgRenderer : IDisposable > { > void DrawFragment(SvgFragment svgFragment); > void DrawImage(SvgImage svgImage); > void DrawSwitch(SvgSwitch svgSwitch); > void DrawSymbol(SvgSymbol svgSymbol); > void DrawUse(SvgUse svgUse);...

> If we split the library, then the new manipulation-only library shouldn't have any method related to drawing. the question is then, who is responsible for traversing the element tree...

hello, this sounds totally interesting and actually we are also planning to use SkiaSharp internally in other projects and have looked into it quite recently. so that would fit quite...

we had a short chat about the merge and came to the conclusion that it would be better for us to schedule the merge bit further. even as far as...

hello @gentledepp how is the status of the fork on your end? do you still maintain it? maybe its more easy to release a final version of this master branch...

great, thanks for the update!

ideally we would merge the current master with the skiasharp master and combine all fixes. however, this sounds like a huge job and i am not sure whether we have...

i have never tried them... could you debug it and make a pull request?