Re: Properties of Custom Paint

On Tue, May 19, 2015 at 3:52 PM, Amelia Bellamy-Royds
<amelia.bellamy.royds@gmail.com> wrote:
> Even better!
>
> So this could potentially address lots of the live path effects features
> that the Inkscape team has been implementing: draw a shape with a sketchy
> outline that doesn't quite line up with the geometric shape, or with
> variable-width strokes, or all sorts of fun things where the rendered output
> is calculated as an extension of the basic shape.
>
> However, if that's the end goal then I think it should be more clearly
> spelled out on Ian's list.
>
> If you want to be able to paint an extra effect on an element, you don't
> want to have to re-write all the code for rendering the basic features.  So
> you need to be able to access the current rendering process as a series of
> calls, so that you can replace any of them, modify any of them (e.g., take
> the result of the browser's draw-border routine and apply a graphical effect
> to it), or insert a new call anywhere in the list.
>
> I think this is what the "Custom paint augments existing elements in the
> DOM" point is getting at.  But it's more than just augmenting the existing
> DOM elements -- it's about augmenting the existing rendering model.  A
> filter augments the existing DOM element, but only after the browser has
> rendered and rasterized it.  If you wanted to add a border-filter property,
> you need a greater granularity of control.

Yeah, sorry, you're missing a lot of context - the idea that you can
just invoke "paint my text as normal" (or border, or etc) is
definitely part of it.  You can skip phases or put arbitrary
additional effects before/between/after phases.

~TJ

Received on Tuesday, 19 May 2015 20:13:08 UTC