[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: RE: [platform-swt-dev] org.eclipse.swt.SWT
|
>>>>> If your argument is that the current SWT API is a "lean and mean"
stripped
>>>>> down version written for speed over accuracy, well great, but then you
need
>>>>> a wrapper layer around it for more traditional programming that does
all the
>>>>> error checking ...
Why not write the wrapper? There seem to be at least one project (SWEET)
doing so.
>>>>> ... and convenience coding that makes something usable by less
>>>>> adventurous programmers (that is, most of us).
None of this is stopping people from using SWT. If SWT is considered "hard",
it will be for the same reasons AWT and Swing are considered "hard", while
Visual Basic is considered "easy".
There is perhaps a strong demand for tools that enable these programmers to
drag & drop non-descript widgets onto a form, double-click them and then
copy & paste SQL from a QueryByExample tool into the event handlers.
I'm sure you're right, but I was attracted by SWT because it was not like
that. It's a bit rough on the edges, but the sourcebase is small and
understandable, while being potent enough to carry the weight of something
like Eclipse.
