make fromHSL public, add toHSL

[Jos Poortvliet]

On 6/13/07, Thomas Zander <zander at kde.org> wrote:
>
> On Wednesday 13 June 2007 10:34:46 Olaf Schmidt wrote:
> > [ Thomas Zander, Mi., 13. Jun. 2007 ]
> >
> > > Last I heard the consensus was still that one color space for kdelibs
> > > is enough.
> >
> > No, there was no consensus in this,
>
> Sure there was;
> read this again;
>
> On Monday 04 June 2007 22:32:30 Aaron J. Seigo wrote:
> >  consensus has been to be conservative on this as we grow towards a
> > better understanding of what is really needed from these colors.
>
>
> > and I object to ignoring the W3C
> > standards that require HSL.
>
> Ehm, nobody is implying any such thing. I'm not sure why you think this,
> but to put your worries at easy I can say that I am sure that KHTML has,
> and will keep having, some code to do the w3c stuff, that is not the
> topic of discussion here.
>
>
> Sorry for being a bit agitated, but its that I am getting a bit tired of a
> weekly thread of Matthew asking again and again and again for public
> KDELIbs API for this color space.


I sure wouldn't want to get involved in this, but I can't resist asking what
solution you then propose for the windows color picker and the themes and
styles and apps like Kate who need this? They must copy-paste the code,
right?

Maybe Matthew can write the code he wanted in KDElibs but place it in
playgroud, and then each of those who need it copy-paste it from there. If
it turns out there are enough users, it can get in KDElibs (before or after
4.0). If only 2 places finally need it, it won't.

Sounds conservative to me, yet it provides what those apps need (at least in
terms of functionality).

--
> Thomas Zander
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070613/5c0b5cde/attachment.htm>