[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Base class for u16 color models?
From:       Casper Boemann <cbr () boemann ! dk>
Date:       2005-08-09 19:29:31
Message-ID: 200508092129.31887.cbr () boemann ! dk
[Download RAW message or body]

On Tuesday 09 August 2005 21:12, Boudewijn Rempt wrote:
> > > And so on... And of course, the same for the 32bit float & integer
> > > colorspace once Adrian has those done. I like the prolog & epilog
> > > composite macros in the 16 bit rgb a lot, by the way :-) -- but maybe
> > > we can move the bitBlt with the switch that actually does calls the
> > > composition routines into KisStrategyColorSpace?
> >
> > but wouldn't that just be duplicated code in every colorspace
>
> No -- at the moment there's a lot of duplicated code; I want to move as
> much of that as possible to the base class and have only the dedicated
> composite ops in the color classes.
oh, I was just talking about the bitblt, from the painter. Do you want to move 
that generic code into every colorspace?

> > > The idea with XYZ is, by the way, to have as accurate a default
> > > implemenation as possible, but one that is slow enough to stimulate us
> > > to provide optimized implementations in the individual colorspaces :-)
> >
> > what do you mean with XYZ
>
> The xyz colorspace -- or should I use lab here? My sources are not in
> agreement about which is the best for a generic fall back.
either one I think. I was just confused, because you hadn't mentioned XYZ 
earlier in the mail at all. But I agree.
-- 
best regards / venlig hilsen
Casper Boemann
_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop

[prev in list] [next in list] [prev in thread] [next in thread]