On Tue, 1 Sep 2026 05:49:46 GMT, Laurent Bourgès <[email protected]> wrote:
> > > * The implementation leverages the software Pisces renderer. > > > * This lays the groundwork for future support of text rendering and path > > > operations. > > > > > > aren't these already implemented in this version? or something is still > > > missing? > > > > > > Right, I'll remove that -- that was before I finished the PoC. > > Since 2016 the Marlin renderer replaced the Pisces renderer to improve > quality & performance... (software ie cpu-bound rendering). @bourgesl Marlin replaced the Pisces rasterizer, but didn't fully replace the whole stack (so parts of Pisces were removed, but not the compositor/painter). So the stack used by `WritableImage` is Marlin + Pisces (sw_prism.dll), which is a full software stack, regardless of what FX itself uses or what you configured (FX will still be fully accelerated). I should have stated this more accurately. > Please clarify if needed: is it using only software rendering (including > blending) or it uses the 'usual' pipeline ie marlin+gpu blending ? For `WritableImage` it will always use Marlin + Pisces painter (so full CPU stack), while other parts of FX can (simultaneously) use the Marlin + D3D/ES2/Metal (GPU) stack. So the demo that is included in this PR is showing you Marlin+CPU (`WritableImage`) and Marlin+GPU (`Canvas`) side by side ------------- PR Comment: https://git.openjdk.org/jfx/pull/1969#issuecomment-5491646332
