[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [E-devel] Premultiply or not
On Sun, Jul 02, 2006 at 12:35:34PM +0900, Carsten Haitzler wrote:
> what i think might be best is we:
> 1. add internal premul to non-premul and back conversion routines (need them
> anyway - may as well make them fast).
> 2. need to add calls to image objects to get/set the COLORSPACE of the internal
> object data (the default would be premul and the suggestion would be to leave
> it alone unless you have very special needs).
> 3. move default colorspace to ARGB_PREMUL (we can have non-premul space, but it
> will need conversion to premul before using in routines).
> 4. i think the best might be we have a evas_colorspace_set(evas,
> EVAS_COLORSPACE_ARGB_PREMUL); for example and a EVAS_COLORSPACE_ARGB and that
> leads to EVAS_COLORSPACE_YUVA as well so then evas can do the conversion (if
> needed) when setting the color of an object on that canvas. this will mean we
> can port existing code with 1 function call when creating the canvas (set it to
> the non premul argb). perhaps also per object too (an objects specific
> colorspace overrides the evas one).
> then we can begin a migration of code over to premul and remove the call - but
> still keep it there for the ability to switch into a more convenient
> colorspace. i am not sure this colorspace should affect image pixels though...
> that should be per image object as above.
+1 Sounds good to me.