Ideal D GUI Toolkit

[Peter Williams]

On 21/05/13 13:46, Tyler Jameson Little wrote:
> I'm completely willing to head up the initial development. I probably
> won't get anything done, and any initial work will be Linux-specific (I
> honestly don't care about Mac OS X or Windows).

Nor me, really.

Nevertheless, I've found using PyGTK means that my GUIs run on 
Mac/Windows provided the users are able to install the command line 
packages that they're wrappers for (where that's necessary).  I will 
admit that I had to do a very small bit of Windows specific code to 
properly run CLI commands and capture their output (20 or 30 lines).

> If anything does get
> done, I'll definitely come back here to get help on the design. I'm
> willing to do some leg-work, but I'm not experienced in any way, shape
> or form with GUI development (most of my work is server-type stuff in Go
> or front-end stuff in JS/HTML5/CSS3).
>
> If we're generally in agreement that a UI toolkit is a good direction,
> I'd love to waste the next few months of my life doing something that
> likely won't go anywhere. I personally think it's much more exciting to
> make something in native D instead of trying to work around the lack of
> concern other C++ toolkits like Qt have for cross-language portability.

Yes, if D aspires to be a systems programming language it can't keep 
relying on wrappers around C/C++ libraries (especially C++).  In the 
long term, it should be D all the way down to the OS API.

Peter