Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Novice Newsgroups: comp.lang.java.programmer Subject: Re: Swing is dead! Long live Swing. Date: Fri, 17 Feb 2012 16:35:24 +0000 (UTC) Organization: Your Company Lines: 73 Message-ID: References: <4f3d91f3$0$291$14726298@news.sunsite.dk> NNTP-Posting-Host: iD3daMmo7WQHmRS5dsV5WQ.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org User-Agent: Xnews/5.04.25 X-Antivirus-Status: Clean X-Notice: Filtered by postfilter v. 0.8.2 X-Antivirus: avast! (VPS 120217-0, 2012-02-17), Outbound message Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:12124 Arne Vajhøj wrote in news:4f3d91f3$0$291$14726298@news.sunsite.dk: > On 2/16/2012 2:13 PM, Novice wrote: >> Knute Johnson wrote in >> news:jhhsv4$uov$1 @dont-email.me: >>> I was doing some investigation of JavaFX and found a Q&A on the >>> javafx.com website. >>> >>> "6. Is JavaFX replacing Swing as the new client UI library for Java >>> SE? Yes. However, Swing will remain part of the Java SE >>> specification for the foreseeable future, and is included in the >>> JRE. On one hand, Swing is widely used in existing Java desktop >>> applications, but relies on an old architecture, which requires a >>> certain level of expertise and specialization. On the other hand, >>> JavaFX features a set of modern UI controls that can be skinned >>> using standard CSS techniques. While we recommend developers to >>> leverage JavaFX APIs as much as possible when building new >>> applications, it is possible to use Swing and JavaFX >> within >>> the same application, allowing developers to extend existing Swing >>> applications." >>> >>> I've just started playing with JavaFX and I've got a long way to go >>> to really understand it but it looks fairly simple. I don't know >>> what it is going to be like to produce the type of GUI interfaces >>> that I >> usually >>> do for work with it though. >>> >>> Maybe we need a comp.lang.java.fx group. >> >> My sole experience with JavaFX is the couple of hours I've spent >> messing around with it this morning so I don't speak from any great >> expertise. However, given the fact that JavaFX only works in Windows >> XP/Vista/7 at the moment - a Mac version exists but is apparently not >> that mature yet and a Linux version is anticipated _eventually_ - I >> submit that JavaFX may not be worthy of a great deal of development >> effort yet, at least for those who want to develop things that are >> going to run on multiple platforms, some of which _aren't_ Windows. >> >> It may be "the next big thing" before too long and it may be worth >> investing some time to learn now rather than jumping on the bandwagon >> later but I'm not inclined to put much time into it until it's clear >> that it will be made available for all the platforms on which we >> expect to run our Java code. A statement of commitment indicating >> that Mac and Linux versions WILL be available at the same or similar >> level to the Windows versions by some not-too-distant date is >> probably all I need to get more enthusiastic about JavaFX.... > > Did you read the text you commented on? > > "6. Is JavaFX replacing Swing as the new client UI library for Java > SE? Yes." > > It says that JavaFX will become part of Java SE. > > Then it will be on all platforms with (that version > or higher of) Java SE. > That will be fine when it is true but my point was that it this hasn't happened yet and Oracle hasn't committed to a specific date when it will happen. I'm just a little leery about vaporware. It wouldn't be the first time something like this was promised and then failed to happen for one reason or another. It might be a little premature to embrace JavaFX given that Oracle's intentions may not materialize. -- Novice