Ideal D GUI Toolkit

Nick Sabalausky SeeWebsiteToContactMe at semitwist.com
Mon May 20 14:17:40 PDT 2013


On Mon, 20 May 2013 13:36:42 -0700
Timothee Cour <thelastmammoth at gmail.com> wrote:

> The following will take much less time and can achieve good, native
> results quickly:
> 
> Design a user-code facing clean api using idiomatic D (front end
> code): windows, widgets, callbacks via delegates, etc.
> Design a glue layer to talk to different backends: gtkd, wxd, qtd,
> fltk etc.
> 
> This is what python does with matplotlib:
> http://matplotlib.org/faq/usage_faq.html : they support pygtk,
> wxpython, tkinter, qt, macosx, or fltk, and also non interactive
> backends) The user code stays clean, the results are native
> (depending on backend), and the wheel is not reimplemented.
> 

Yea, that would definitely be my approach, too.



More information about the Digitalmars-d mailing list