On Mon, Sep 20, 2010 at 1:39 PM, Jess Holle <[email protected]> wrote: > Well if they give JavaFX a *really* nice Java API so one can use it from > Java as easily as Swing, then there's nothing more compelling about SWT due > to this announcement. > > SWT has no point over Swing at this point (vs. when it was originally > created) unless you or your users are *really *hung up on widgets or fonts > tracking the native platforms *perfectly*. Some of us really and truly > could care less. >
You probably mean "could not care less", otherwise you're agreeing with me :-) A lot of people care about applications looking like the host OS they are running in, and SWT/JFace/EclipseRCP is way ahead of Swing in that area. > 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. 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. -- Cédric -- 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.
