Nick Sabalausky wrote:
What does this mean ? If wxWidgets is being ported to D2 ?
Or if you can use wxWidgets from D2, if so: yes you can.
Or at least you could, back with DMD 2.049 (or whatever)
But what should be done is to regenerate it with SWIG/etc.
Even if wxD "works" with D2 and wx3 too, it's still a port
from wx.NET and wxWidgets 2.6.4 API - and 5 years old now.
Ahh, I was under the impression there were currently no wd bindings for D2,
just D1. Am I correct in my understanding that wx is cross-platform and uses
native controls?
You are correct. Where native means Win32/Win64 or GTK+ or Carbon/Cocoa.
There's even a Qt4 port coming next to the GTK+, and an old limited X11.
wxD uses wx.NET as a base, where wxHaskell uses wxEiffel, but same idea.
Drew some images and stuff on http://wxd.sourceforge.net/ to explain it.
Also, as I haven't followed this real closely, what's the current state of
SWIG for D? Fully-usable?
No idea. But I saw that just like GCC it comes with Go language support.
Just saying that the "correct" approach is to generate it from the C++ ?
The current export "C" code is generated by a mix of Perl and monkeys...
See http://xkcd.com/224/ for some related information on how that works.
--anders
