Skip to main content

Implications of JavaFX Version 2.0

4 replies [Last post]
swebb
Offline
Joined: 2010-03-10
Points: 0

So with the news from JavaOne still be absorbed what are peoples feelings about the impact of the change in direction of JavaFX and the impact on any current Swing development from the community in general?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kschaefe
Offline
Joined: 2006-06-08
Points: 0

Oracle is going to remain committed to Swing, but much less so than before. Major issues will be fixed; some new "small" features or components will be added, but most new work is done.

Now, I think that two things happen:
1. The importance of OpenJDK increases. Perhaps the best way to get fixes into the JDK is to do it yourself. There are several long-standing JMenu issues that would take less than one hour to fix, but there are not high priority issues. If your company needs that to be fixed; maybe you have to do it yourself. In the open-source world, this is the way things get done; you contribute back to the project.

2. Projects such as SwingX become more important. With much shorter lifecycles between releases than the JDK, it becomes easier to fix and workaround isses. The incubator is full of cool ideas that we can flesh out, plus new Swing ideas come around daily. SwingX and other projects will help drive Swing forward.

Swing is going to be with us a long time. With at least 5, probably 10 more years of active client development, followed by another 10 years of maintenance. So, I think the future of Swing is good for the time-being.

Karl

PS. Steve, send me an email to my java.net address, I tried to send you one, but got no response.

Fabrizio Giudici

On 9/23/10 06:42 , jdnc-interest@javadesktop.org wrote:
> So with the news from JavaOne still be absorbed what are peoples feelings about the impact of the change in direction of JavaFX and the impact on any current Swing development from the community in general?

My impression is that the community will continue to use Swing as usual
and will enjoy, hopefully soon (indeed, this J1 has been the
fourth-JavaFX-announce-in-a-row), new components form JavaFX. I'm
particularly eager to get the f*cking video codecs, at last.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Fabrizio Giudici

On 9/23/10 06:42 , jdnc-interest@javadesktop.org wrote:
> So with the news from JavaOne still be absorbed what are peoples feelings about the impact of the change in direction of JavaFX and the impact on any current Swing development from the community in general?

My impression is that the community will continue to use Swing as usual
and will enjoy, hopefully soon (indeed, this J1 has been the
fourth-JavaFX-announce-in-a-row), new components form JavaFX. I'm
particularly eager to get the f*cking video codecs, at last.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

osbald
Offline
Joined: 2003-06-13
Points: 0

Not wanting to speak out of turn for more regular contributors but I'd say it changes relatively little. If anything it probably makes SwingX all the more important as its clear the hiatus on the official support & enhancement of Swing has become somewhat more permanent. The upkeep of Swing its therefore up to the community, use it or lose it.

SwingX is still active, new components and deployment options are on the way and we hope the upcoming java.net migration will be kind to us and some key related Swing APIs that may have lost active maintainers: timingframework, swingworker, swinglayout, wizard, appframework, beanbindings, jdnc-incubator (new name please) etc.. Because they know you really wont like Jeannette when shes angry ;)

PS. Does Swinglabs need a new lead?