On 9/20/2010 3:49 PM, Cédric Beust ♔ wrote:
Just give us a decent UI that runs on any desktop OS without any
extra native libraries, etc (which kills the notion of SWT
immediately)
How so? Swing uses native libraries as well (well, AWT does). They are
just implementing the UI at a different level than SWT.
The whole "native libraries are evil" thing died more than ten years ago.
Swing uses native libraries *but* they're a built in part of Java SE and
part and parcel of having a Java SE implementation.
Native libraries outside this *are* evil for anyone who deals with more
than a couple of platforms. They're a royal PITA for client work in
this case.
and a reasonable API (which Swing has in my book). The rest of
the Eclipse RCP might be nice -- but it's "contaminated" by SWT
for those who want no part of SWT.
Sounds like a pretty arbitrary and emotional position, but whatever
works for you.
It's not arbitrary in that SWT takes too much work to deploy, run,
troubleshoot, etc, when you have to support numerous platforms. There
really is a realm for "works well enough everywhere" UIs -- that's
really the entirety of HTML/JavaScript UIs, for starters.
Back to the original topic, if JavaFX's rendering engine and APIs are
rolled into Java SE implementations than that would be yet another
reason to stay away from SWT. If JavaFX is just yet another add-on
library requiring its own add-on native libraries, then it's still on no
worse ground than SWT.
--
Jess Holle
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
