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.
On Mon, 20 May 2013 12:41:08 -0700
"Adam Wilson" <flyboynw@gmail.com> wrote:
> On Mon, 20 May 2013 12:28:16 -0700, Dmitry Olshansky
> <dmitry.olsh@gmail.com> wrote:
> >
> > Markup for GUI layout seems like a decent idea.And what takes that markup and actually executes it? Magical GUI
> >
>
> HTML is markup. XAML is markup. QML is markup. XUL is markup. iOS is
> markup. Android is markup. Realistically, the age of OS native
> toolkits has passed, markup is the future. *shrug* For me it's a
> practical thing,
fairies? ;)
Markup is, by necessity, nothing more than a front-end for a
code-based GUI engine/toolkit/whatever-we-want-to-call-it. The GUI
toolkits will always be there whether it's the UI designers that use it
directly or the markup developers that use it directly.
I don't know where you got that idea.
>markup is extensible, OS widgets are not.
>