Something that creates an API bridge between different external
libraries is naturally a good fit for Phobos and exactly type of
additions I'd like to see there. I think only concern is where
exactly to put it : std.media.image.colour sounds like a most
fitting qualified path to me but that is quite the hierarchy for
a single module :)
- Re: Phobos colour module? Rikki Cattermole via Digitalmars-d
- Re: Phobos colour module? Jacob Carlborg via Digitalmars-d
- Re: Phobos colour module? Manu via Digitalmars-d
- Re: Phobos colour module? via Digitalmars-d
- Re: Phobos colour module? Manu via Digitalmars-d
- Re: Phobos colour module? Peter Alexander via Digitalmars-d
- Re: Phobos colour module? Phil via Digitalmars-d
- Re: Phobos colour module? Manu via Digitalmars-d
- Re: Phobos colour module? Manu via Digitalmars-d
- Re: Phobos colour module? David Nadlinger via Digitalmars-d
- Re: Phobos colour module? Dicebot via Digitalmars-d
- Re: Phobos colour module? Manu via Digitalmars-d
- Re: Phobos colour module? ponce via Digitalmars-d
- Re: Phobos colour module? Manu via Digitalmars-d
- Re: Phobos colour module? ponce via Digitalmars-d
- Re: Phobos colour module? Manu via Digitalmars-d
- Re: Phobos colour module? Brad Anderson via Digitalmars-d
- Re: Phobos colour module? Manu via Digitalmars-d
- Re: Phobos colour module? via Digitalmars-d
- Re: Phobos colour module? Adam D. Ruppe via Digitalmars-d
- Re: Phobos colour module? via Digitalmars-d