Re: daffodil, a D image processing library

2016-07-06 Thread Martin Nowak via Digitalmars-d-announce
On Friday, 1 July 2016 at 21:18:28 UTC, Vladimir Panteleev wrote: In case anyone from this thread haven't seen it, I have my own image library, which I wrote about here: https://blog.thecybershadow.net/2014/03/21/functional-image-processing-in-d/ There is also a very nice and somewhat popular

Re: daffodil, a D image processing library

2016-07-04 Thread Edwin van Leeuwen via Digitalmars-d-announce
On Monday, 4 July 2016 at 15:10:30 UTC, Manu wrote: On 1 July 2016 at 18:19, Edwin van Leeuwen via Digitalmars-d-announce wrote: On Friday, 1 July 2016 at 08:11:37 UTC, Benjamin Schaaf wrote: On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole

Re: daffodil, a D image processing library

2016-07-04 Thread Manu via Digitalmars-d-announce
On 1 July 2016 at 18:19, Edwin van Leeuwen via Digitalmars-d-announce wrote: > On Friday, 1 July 2016 at 08:11:37 UTC, Benjamin Schaaf wrote: >> >> On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole wrote: >>> >>> On 01/07/2016 9:35 AM, Benjamin Schaaf

Re: daffodil, a D image processing library

2016-07-02 Thread Relja Ljubobratovic via Digitalmars-d-announce
On Friday, 1 July 2016 at 21:18:28 UTC, Vladimir Panteleev wrote: Generally most use cases for using an image library can be divided into: 1. You have full control over the images being loaded. This is the case when you're loading graphical assets for your application which otherwise

Re: daffodil, a D image processing library

2016-07-01 Thread Benjamin Schaaf via Digitalmars-d-announce
On Friday, 1 July 2016 at 23:37:59 UTC, Leandro Lucarella wrote: On Thursday, 30 June 2016 at 21:35:37 UTC, Benjamin Schaaf wrote: Alongside I've also written (an admittedly hacky) sphinx (http://www.sphinx-doc.org/en/stable/) extension that provides a domain and autodocumenter for D, using

Re: daffodil, a D image processing library

2016-07-01 Thread Leandro Lucarella via Digitalmars-d-announce
On Thursday, 30 June 2016 at 21:35:37 UTC, Benjamin Schaaf wrote: Alongside I've also written (an admittedly hacky) sphinx (http://www.sphinx-doc.org/en/stable/) extension that provides a domain and autodocumenter for D, using libdparse and pyd. Where can I get the Sphinx extension? :-D

Re: daffodil, a D image processing library

2016-07-01 Thread Vladimir Panteleev via Digitalmars-d-announce
On Friday, 1 July 2016 at 11:09:49 UTC, Relja Ljubobratovic wrote: When loading images, bit depth should be determined in the runtime, depending on the image you'd be loading at the moment. Or am I wrong? Generally most use cases for using an image library can be divided into: 1. You have

Re: daffodil, a D image processing library

2016-07-01 Thread Relja Ljubobratovic via Digitalmars-d-announce
On Friday, 1 July 2016 at 14:30:17 UTC, Benjamin Schaaf wrote: The problem with not knowing bit depth at compile time, is that you're now forced to store the image internally as plain bytes. So if you wanted to add two colors, you end up with ubyte[4] + ubyte[4] instead of int + int. At some

Re: daffodil, a D image processing library

2016-07-01 Thread Michael via Digitalmars-d-announce
On Friday, 1 July 2016 at 11:09:49 UTC, Relja Ljubobratovic wrote: On Thursday, 30 June 2016 at 21:35:37 UTC, Benjamin Schaaf wrote: [...] Hi there. Took a quick look at the source and it seems really nice! I like your idea of extensibility for color conversion. Also, image I/O seems to be

Re: daffodil, a D image processing library

2016-07-01 Thread Benjamin Schaaf via Digitalmars-d-announce
On Friday, 1 July 2016 at 11:09:49 UTC, Relja Ljubobratovic wrote: On Thursday, 30 June 2016 at 21:35:37 UTC, Benjamin Schaaf wrote: daffodil is a image processing library inspired by python's Pillow (https://pillow.readthedocs.org/). It is an attempt at designing a clean, extensible and

Re: daffodil, a D image processing library

2016-07-01 Thread Guillaume Piolat via Digitalmars-d-announce
On Thursday, 30 June 2016 at 21:35:37 UTC, Benjamin Schaaf wrote: daffodil is a image processing library inspired by python's Pillow (https://pillow.readthedocs.org/). It is an attempt at designing a clean, extensible and transparent API. Nice. Minor nitpick, please make the width and

Re: daffodil, a D image processing library

2016-07-01 Thread Relja Ljubobratovic via Digitalmars-d-announce
On Thursday, 30 June 2016 at 21:35:37 UTC, Benjamin Schaaf wrote: daffodil is a image processing library inspired by python's Pillow (https://pillow.readthedocs.org/). It is an attempt at designing a clean, extensible and transparent API. https://github.com/BenjaminSchaaf/daffodil

Re: daffodil, a D image processing library

2016-07-01 Thread Rory McGuire via Digitalmars-d-announce
On Fri, Jul 1, 2016 at 10:11 AM, Benjamin Schaaf via Digitalmars-d-announce wrote: > On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole wrote: > >> On 01/07/2016 9:35 AM, Benjamin Schaaf wrote: >> >>> daffodil is a image processing library inspired by

Re: daffodil, a D image processing library

2016-07-01 Thread Edwin van Leeuwen via Digitalmars-d-announce
On Friday, 1 July 2016 at 08:11:37 UTC, Benjamin Schaaf wrote: On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole wrote: On 01/07/2016 9:35 AM, Benjamin Schaaf wrote: Doesn't use allocators or Manu's color work, yup yup not interested. In terms of std.experimental.color, one of the

Re: daffodil, a D image processing library

2016-07-01 Thread Benjamin Schaaf via Digitalmars-d-announce
On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole wrote: On 01/07/2016 9:35 AM, Benjamin Schaaf wrote: daffodil is a image processing library inspired by python's Pillow (https://pillow.readthedocs.org/). It is an attempt at designing a clean, extensible and transparent API.

Re: daffodil, a D image processing library

2016-06-30 Thread ketmar via Digitalmars-d-announce
On Friday, 1 July 2016 at 01:47:44 UTC, Jack Stouffer wrote: Way to be a dismissive asshole. why so serious? it is clearly a joke.

Re: daffodil, a D image processing library

2016-06-30 Thread ketmar via Digitalmars-d-announce
On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole wrote: Doesn't use allocators great library! definitely worth a closer look.

Re: daffodil, a D image processing library

2016-06-30 Thread rikki cattermole via Digitalmars-d-announce
On 01/07/2016 1:47 PM, Jack Stouffer wrote: On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole wrote: Doesn't use allocators or Manu's color work, yup yup not interested. Way to be a dismissive asshole. Let me rewrite that sentence for you: "Hey, nice work, we really need something

Re: daffodil, a D image processing library

2016-06-30 Thread Jack Stouffer via Digitalmars-d-announce
On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole wrote: Doesn't use allocators or Manu's color work, yup yup not interested. Way to be a dismissive asshole. Let me rewrite that sentence for you: "Hey, nice work, we really need something like this. I'm a bit concerned about the GC

Re: daffodil, a D image processing library

2016-06-30 Thread rikki cattermole via Digitalmars-d-announce
On 01/07/2016 9:35 AM, Benjamin Schaaf wrote: daffodil is a image processing library inspired by python's Pillow (https://pillow.readthedocs.org/). It is an attempt at designing a clean, extensible and transparent API. https://github.com/BenjaminSchaaf/daffodil

daffodil, a D image processing library

2016-06-30 Thread Benjamin Schaaf via Digitalmars-d-announce
daffodil is a image processing library inspired by python's Pillow (https://pillow.readthedocs.org/). It is an attempt at designing a clean, extensible and transparent API. https://github.com/BenjaminSchaaf/daffodil https://benjaminschaaf.github.io/daffodil/ The library makes full use out of