User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721
We are looking at the benefits/pitfalls of moving our in-house Java
development to using SWT/JFace.
Due to the widget set being tied with the IDE, those features that could
be implemeted to make application programming using the widgets easier,
will not be. This is because, changes will only be started if Eclipse
requires them.
I am hearing (more increasingly) that developers are now stating to use
SWT/JFace for their client side applications as an alternative to Swing.
I will not get into that debate hear, but would just like to say that
after looking at both, SWT looks the smarter choice.
What we need now is for SWT/JFace to be split off into a project in its
own right. This would ensure that it could have functionality added,
even if eclipse did not use them, but would be of use to the stand-alone
application developer.