<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><blockquote type="cite"><div dir="ltr"><span>* Graphics architecture (Thorsten)</span><br><span> * https://pad.documentfoundation.org/p/ESC_graphics_architecture</span><br><span> * skia / vulkan metabug: https://bugs.documentfoundation.org/show_bug.cgi?id=129062</span><br><span> + 13 (+1) open bugs, 141 total (+1)</span><br><span></span><br><span>* QA update (Xisco)</span><br><span> + Please help flesh out the monthly reports:</span><br><span> https://nextcloud.documentfoundation.org/s/2qbepFYXXan4ief</span><br></div></blockquote><br><div>I hope I am not speaking out of turn, but one thing that might help in untangling VCL would be to ensure that the actual drawing work be done in SalGraphics, and not in OutputDevice.</div><div><br></div><div>I recently logged a bug here:</div><div><br></div><div><a href="https://bugs.documentfoundation.org/show_bug.cgi?id=139170">https://bugs.documentfoundation.org/show_bug.cgi?id=139170</a></div><div><br></div><div>The example given is that code that actually determines a polyline needs to be “emulated”. What this means is that the polyline and polygon rendering is ing done in OutputDevice and not in the various SalGraphics backends. In particular, the genpsp and X11 backends are the backends that don’t seem to handle things fully.</div><div><br></div><div>OutputDevice also seems to handle things that other classes should be handling - for example it seems to do more handling of bitmaps where I would have thought that the Bitmap class could handle the functionality.</div><div><br></div><div>Just a general comment. I have recently taken a stab at shifting some functionality out of OutputDevice and into Bitmap, but there is a lot I can see we could cull from OutputDevice.</div><div><br></div><div>Chris</div></body></html>