wrote:
>>
>> I think I'm about as happy with my colour lib as I'm going to be. It
>> really needs reviews.
>>
>> I added packed-RGB support, including weird micro-float and
>> shared-exponent formats.
>> They're important for interacting with
On Monday, 12 September 2016 at 04:14:27 UTC, Manu wrote:
I think I'm about as happy with my colour lib as I'm going to
be. It really needs reviews.
I added packed-RGB support, including weird micro-float and
shared-exponent formats.
They're important for interacting wit
I think I'm about as happy with my colour lib as I'm going to be.
It really needs reviews.
I added packed-RGB support, including weird micro-float and
shared-exponent formats.
They're important for interacting with any real-time rendering libraries.
There is only one texture form
On 4 September 2016 at 03:44, Marco Leise via Digitalmars-d
wrote:
> Am Sat, 3 Sep 2016 16:01:26 +1200
> schrieb rikki cattermole :
>
>> On 03/09/2016 12:17 PM, Manu via Digitalmars-d wrote:
>> ...snip...
>>
>> > I think the presence of all this colour space information as type
>> > arguments shou
On 04/09/2016 5:44 AM, Marco Leise wrote:
Am Sat, 3 Sep 2016 16:01:26 +1200
schrieb rikki cattermole :
Something[0] along this line perhaps?
Overview of the choices and scope along with reasoning.
[0]
https://github.com/rikkimax/alphaPhobos/blob/master/source/std/experimental/graphic/image/spe
Am Sat, 3 Sep 2016 16:01:26 +1200
schrieb rikki cattermole :
> On 03/09/2016 12:17 PM, Manu via Digitalmars-d wrote:
> ...snip...
>
> > I think the presence of all this colour space information as type
> > arguments should nudge users in the right direction. They'll be all
> > "I've never seen th
On 03/09/2016 12:17 PM, Manu via Digitalmars-d wrote:
...snip...
I think the presence of all this colour space information as type
arguments should nudge users in the right direction. They'll be all
"I've never seen this parameter before..." and google it... maybe.
I don't think it's the std lib
On 3 September 2016 at 03:25, Marco Leise via Digitalmars-d
wrote:
> Am Fri, 2 Sep 2016 15:58:05 +1000
> schrieb Manu via Digitalmars-d :
>
>> I wonder, should NormalizedInt be a module beneath the color package,
>> or should it be a separate module in its own right?
>> I don't know of uses for th
On 2 September 2016 at 22:36, Steven Schveighoffer via Digitalmars-d
wrote:
> On 8/31/16 1:58 AM, Manu via Digitalmars-d wrote:
>>
>> I have this implementation issue, which I'm having trouble applying
>> good judgement, I'd like to survey opinions...
>>
>> So, RGB colours depend on this 'normalis
Am Fri, 2 Sep 2016 15:58:05 +1000
schrieb Manu via Digitalmars-d :
> On 2 September 2016 at 06:09, Marco Leise via Digitalmars-d
> wrote:
> > I'd suspect #1 to be the best option, too. However, I don't
> > know when users will deal with these calculations.
>
> Neither do I, it's just that Norm
> Is it s or z ? :)
It's an alias to forego any language bike shedding.
On 8/31/16 1:58 AM, Manu via Digitalmars-d wrote:
I have this implementation issue, which I'm having trouble applying
good judgement, I'd like to survey opinions...
So, RGB colours depend on this 'normalised integer' concept, that is:
unsigned: luminance = val / IntType.max
signed: luminance
On 2 September 2016 at 06:09, Marco Leise via Digitalmars-d
wrote:
> Am Wed, 31 Aug 2016 15:58:28 +1000
> schrieb Manu via Digitalmars-d :
>
>> I have this implementation issue, which I'm having trouble applying
>> good judgement, I'd like to survey opinions...
>>
>> So, RGB colours depend on this
Am Wed, 31 Aug 2016 15:58:28 +1000
schrieb Manu via Digitalmars-d :
> I have this implementation issue, which I'm having trouble applying
> good judgement, I'd like to survey opinions...
>
> So, RGB colours depend on this 'normalised integer' concept, that is:
> unsigned: luminance = val / IntT
On Wed, 31 Aug 2016 19:33:24 +1000, Manu via Digitalmars-d wrote:
> On 31 August 2016 at 17:58, Andrea Fontana via Digitalmars-d
>> I always think the perfect colour library should work using a superset
>> of all colour spaces, for example cie xyz (is it a superset, isn't
>> it?). isColour(T) then
On Wednesday, 31 August 2016 at 09:37:41 UTC, Andrea Fontana
wrote:
So maybe I miss (more than) something reading source code. You
should write a readme to explain how it works :)
I can probably chip in and help here at some point (both with
documentation and ensuring the API is intuitive).
On Wednesday, 31 August 2016 at 09:33:24 UTC, Manu wrote:
On 31 August 2016 at 17:58, Andrea Fontana via Digitalmars-d
wrote:
On Wednesday, 31 August 2016 at 06:17:15 UTC, Manu wrote:
On 31 August 2016 at 16:01, Chris Wright via Digitalmars-d
wrote:
The color models I'm aware of are HSV,
On 31 August 2016 at 18:04, Andrea Fontana via Digitalmars-d
wrote:
> On Wednesday, 31 August 2016 at 07:58:36 UTC, Andrea Fontana wrote:
>
> I forgot that in this way it's quite easy to wrap external class/struct to
> make them works with library. If we have a custom COLOR class provided by
> ano
On 31 August 2016 at 17:58, Andrea Fontana via Digitalmars-d
wrote:
> On Wednesday, 31 August 2016 at 06:17:15 UTC, Manu wrote:
>>
>> On 31 August 2016 at 16:01, Chris Wright via Digitalmars-d
>> wrote:
>>>
>>> The color models I'm aware of are HSV, HSL, RGB[A], CMYK, Lab, Pantone,
>>> and the Op
On Wednesday, 31 August 2016 at 07:58:36 UTC, Andrea Fontana
wrote:
I always think the perfect colour library should work using a
superset of all colour spaces, for example cie xyz (is it a
superset, isn't it?). isColour(T) then IMO should check if
x,y,z properties exists (or toXYZ() method).
On Wednesday, 31 August 2016 at 06:17:15 UTC, Manu wrote:
On 31 August 2016 at 16:01, Chris Wright via Digitalmars-d
wrote:
The color models I'm aware of are HSV, HSL, RGB[A], CMYK, Lab,
Pantone, and the Open Colour Standard.
I'll initially support, XYZ/xyY, RGB (which is a gigantic set),
HS
On 31 August 2016 at 16:01, Chris Wright via Digitalmars-d
wrote:
> The color models I'm aware of are HSV, HSL, RGB[A], CMYK, Lab, Pantone,
> and the Open Colour Standard.
I'll initially support, XYZ/xyY, RGB (which is a gigantic set), HSx, Lab, Yuv.
> I'm not sure what common operations they h
The color models I'm aware of are HSV, HSL, RGB[A], CMYK, Lab, Pantone,
and the Open Colour Standard.
I'm not sure what common operations they have. Perhaps you could provide
a link to your existing library?
I have this implementation issue, which I'm having trouble applying
good judgement, I'd like to survey opinions...
So, RGB colours depend on this 'normalised integer' concept, that is:
unsigned: luminance = val / IntType.max
signed: luminance = max(val / IntType.max, -1.0)
So I introduce Norm
On 31 August 2016 at 15:01, rikki cattermole via Digitalmars-d
wrote:
>
> 2. As part of your argument I personally would prefer that it is at least
> tested in the context of an image library. We don't want any hidden problems
> there even if that is not your goal to implement the best image libra
So I'm replying without your post, so I will put my thoughts here:
1. Trust your gut on this one, your the expert in the problem domain,
we're not.
2. As part of your argument I personally would prefer that it is at
least tested in the context of an image library. We don't want any
hidden prob
l/un-contentious. It can grow in the future as
desired.
There is a slightly blurry line separating a colour lib from an image
lib, and I want to focus the boundaries.
My design propositions are this:
1. Colour type definitely belongs in the std library;
- Colour types and conversions are ha
101 - 127 of 127 matches
Mail list logo
