It was a long and painful way until i managed to do my tool using gtkD1. Well just after I had finished my port to gtkD I was told that I should give DWT2 another try.
I must confess I wasn’t expecting much after my last experiences with a SWT port. But DWT really is mature. I got it to build very fast and the snippets helped me a lot learning the usage. The lib design comes more natural to me than gtkD and I had the same results in a fraction of the time it took me to tame gtkD. Now my CLInfo Tool3 is DWT based.
DWT in short
Pro:
- Much more intuitive design – I didn’t even miss the gui designer
- Better documentation with a lot of example snippets
- No need to ship a bunch of dependencies with the binary
Con:
- Not absolutely everything of the SWT is ported yet
- No gui designer
- Build script uses rake4 – one more dependency for users of the lib
All in all my conclusion for now is going with DWT for GUI applications in D. At least if it stands the test under linux. But that is still to come..