Where is JWebPane?
JavaFX 1.0 was released last week, and it’s great that it’s out for Windows, but there are lots of things missing from it (like support for OSX or Linux). The biggest missing item for me is the Webkit browser component called JWebPane. I have been looking forward to using this component for months now, and it’s still not out. I visited the blog of the author of this component, and this is what he said:
“Sorry for a significant delay with answer. JavaFX 1.0 release is of very high priority for Sun, and we do our best to release it is the best quality. Unfortunately, JWebPane component is not as stable now, so it will not be a part of 1.0 Uur current plans are to open JWebPane right after 1.0 is released, roughly in a couple of months.”
Posted by: ixmal on September 29, 2008 at 01:34 AM
“Good news is that this delay allows JWebPane team to spend some time on plugins support. Watch for updates”
Posted by: ixmal on September 29, 2008 at 01:37 AM
Marketing brought to you by retarded monkeys
Ok, now to the JavaFX SDK. I don’t like Sun’s marketing message, the main themes of which are:
Wow. That’s some horrendous marketing. Talk about over promising and under delivering!
Yet another f**king scripting language to waste my time
My reaction is that I don’t want to learn another f**king language to do what Swing should already do. Why not put animation controls in the layout manager classes, for instance; why create this alternate toolkit that’s rooted in Swing (JComponent is the root class for both APIs) but the API is divergent with Swing. After being burnt by using SwingX for a while, it’s sad to see another non-consolidated API offering from Sun (not the first, nor the last).
The SceneGraph API is great, but it’s missing JWebPane, and an editor component, and lots of other controls, so it’s USELESS for building anything more complex than say a glorified calculator. The web service connectors are woefully inadequate. Use a JSON library and my Task API, you will have more hair left at the end of the day . The media framework is a good start, but they don’t supply the tools to encode video on the Java cross platform format?! For JavaFX v1 the strategy seems to be to support native video on it’s native platform – so why even use Java? . It seems some retarded monkeys are not only doing the marketing but also have a hand in creating the strategic roadmap.
What else, did I mention that I hate having to learn another freaking scripting language? I don’t want to adopt JavaFX Script and it’s new paradigm for wasting my time. Anyway, there are others who have done this sort of API more elegantly, without a huge budget or workforce – check Galileo out. I don’t like that Sun is pushing this FX Script crap on developers – there is pure Java access to the APIs in JavaFX, so if you wanted you could use your Java code to use the new SceneGraph API and leverage some of the effects in there…
Overall, I’m disappointed at this release. Why not call this a Beta release, instead of 1.0?
Let me know if you’re using FX Script in real world software, and not just dinky demos. I get the feeling that outside of Sun, no one cares about JavaFX, at least the way in which they package, define, and market the set of technologies they call JavaFX.
|« Community for car and watch nuts :)||JWebPane (WebKit for Java) details »|