Linked by Thom Holwerda on Thu 14th May 2009 15:39 UTC
Thread beginning with comment 363664
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
I opened it because this night I should implement trees.
But seeing that it deal with Java SWT, Beeuuuu :-*
I will implement it in Qt anyway, this night and in C++.
(maybe python who knows !)
But seeing that it deal with Java SWT, Beeuuuu :-*
I will implement it in Qt anyway, this night and in C++.
(maybe python who knows !)
So whats wrong with Java according to you?
Or you just want to show off that you can hack something in C++?
There's no point going into a Java vs C++ argument here -- the question is one of toolkit design. Qt is an exceptionally well-designed toolkit (and has Java bindings, remember), but not everyone is fortunate enough to be in a position to use it, and in some situations it may not be appropriate.
Personally, I disliked the design of both the SWT and Swing toolkits when we studied them at university, but if I were required to write something using SWT, this article would be useful, so good job!
Now how about a series of articles comparing widget toolkits -- Qt, GTK, wxWidgets, FLTK, etc...?





Member since:
2009-04-18
I opened it because this night I should implement trees.
But seeing that it deal with Java SWT, Beeuuuu :-*
I will implement it in Qt anyway, this night and in C++.
(maybe python who knows !)