Well if you let me decide between software rendering on client or
software rendering on server, I would prefer the latter.
It's not that clear cut. At least some of the motivation behind Render is
about moving time-consuming operations into the client, notably font
rasterisation.
There are
Wasn't the reason to do font rasterization primiary to give applications
more control over font rendering?
If memory serves, Keith was trying to find a design to solve both issues
with core fonts -- lack of flexibility and latency. There was an extended
brain-storming session on the old
Trapezoids for example would require implementing a rasteriser in shaders.
Pretty much everything that doesn't get accelerated these days requires
shaders.
Tomorrow someone might come and ask for a different type of gradient, why
even bother?
Well if you let me decide between software
Currently there exist several operations in xrender that are better
off client side or through some other graphic api (imo). Think of
trapezoid rasterisation, gradient rendering, etc. Doing this stuff
client side avoids unforseen migration issues and doesn't create any
false impressions with the
Hi,
Currently there exist several operations in xrender that are better
off client side or through some other graphic api (imo). Think of
trapezoid rasterisation, gradient rendering, etc.
Doing this stuff
client side avoids unforseen migration issues and doesn't create any
false impressions
