Graphics Library for D

Jacob Carlborg doob at me.com
Wed Jan 8 04:59:24 PST 2014


On 2014-01-08 12:34, Mike Parker wrote:

> Perhaps. But I would argue that if you need that sort of access then you
> should be using a more specialized library anyway. I'm under the
> impression that what we're discussing here is something simple and easy
> to use. That can cover a wide range of use cases without accessing the
> low level, but would be an impedement if you do need the low level.

The question is how much you're gaining by hiding it.

> Rendering to a memory buffer to generate png images is a legitimate use
> case. If Phobos has a graphics API, I would expect that to be supported
> even when no gpu is present.

Sure, right.

> That's different. A gpu is only required for *hardware accelerated*
> rendering. And I don't think Phobos should require it.

Right.

> Whether it's distributed with the compiler as an optional package or
> simply maintained in the D organization at github and distributed
> through dub, either case is better than making it part of the standard
> lib, IMO. Then more liberty can be taken with the requirements.

It makes a big difference. It's all about what you can expect to be 
available if a D compiler is present.

-- 
/Jacob Carlborg


More information about the Digitalmars-d mailing list