On 14/03/16 10:20, Saša Janiška wrote:
Jaocb Carlborg <d...@me.com> writes:
There's DWT [1] as well.
Wrong URL. ;)
How embarrassing :). Here is the correct URL [1] for reference.
I must admit I'm totally ignorant about Java and I neither use like the
language nor do I use any Java app. :-)
"interface" would in this case refer to the API of the code and not the
GUI of an application.
If you say that "anything that is non-native or doesn't look native is
not acceptable on OS X" what is the advantage of DWT in comparison with
GtkD for Mac OS?
Well, currently there is no support for OS X so if that's a requirement
then DWT will obviously not work. Personally I would not create an
application for OS X at all if it did not have a native GUI.
A couple of years ago I started on an OS X port [2], but I've abandoned
that in favor of automating the porting process [3]. The automated
process is intended to work for all platforms.
If the OS X port was complete, the advantage over GtkD would be that it
would be native.
[1] https://github.com/d-widget-toolkit/dwt
[2] https://github.com/d-widget-toolkit/dwt-mac
[3] https://github.com/d-widget-toolkit/jport/tree/dev
--
/Jacob Carlborg
