Here’s more information on the Java WebKit (JWebPane) component coming with JavaFX for Java SE. There are some interesting comments in that post as well. So far, it sounds great. It should be a very useful component. Here’s an excerpt from this post:
1. HTML Rendering
Since the necessity of employing this component in GUI applications appeared a long time ago, each solution, even simple rendering of web pages, is greatly appreciated. Moreover, in spite of the fact that the importance of interactivity is rising steeply, the correct rendering of up-to-date web content still remains a crucial requirement for an HTML component. It’s worth mentioning that JWebPane copes with this task successfully along with the help of WebKit, one of the most advanced web engines.
2. Load event notifications
Let’s move on to more interesting items. The load control of web pages and its resources is another highly demanded function required by many users. For this purpose JWebPane provides the following events: page loading start, external resource loading start, loading progress, loading stop or error, page loading finish, and resources loading finish. The exact set of events is not finalized yet, and new event types will appear soon.
Sometimes using the HTML component is limited to one document, however, the HTML format itself implies tie-up and cross linking of documents. Navigation control, such as Back, Forward, Get URL and other commands, is naturally provided by JWebPane. The navigation function is closely related to transfers from one page to another. This is quite a controversial point: on the one hand, the application should maintain the history, but on the other hand, the component possesses information about which web sites were visited during the current session. That’s why JWebPane provides the basic tools for history maintenance as well as the ability to retrieve history from the application.
I always wondered where did the "chrome" term come from This term is used to specify the HTML component environment, which is usually a browser window. Chrome typically includes support of the following elements: status bar, window title and icon, tooltips, window size, the component itself, and others. JWebPane, as an HTML component, doesn’t have built-in support of these controls, however, it provides an API to implement those in the application.
JavaOne 2008 Filthy Rich Clients session – Timingframework fix and more
Also a set of slides for this years Filthy Rich Clients session at JavaOne 2008 was released. It’s a very useful session. Check out this link to get all the details (audio + slides). The most interesting thing in this session is a discussion of what slows animations down when using timingframework. I’ve run into this myself. Turns out it’s not the graphics code for your animation, but it’s the timing source. Using the default timing source for the timingframework creates too many threads, and this ends up creating too many events in the EDT, which screws up the timing for your animations. The solution is remarkably simple… just use a static class that creates a single timing source! This is what SceneGraph API does, and even Android’s animation APIs. Here’s a link to the presentation.
|« JDK6 Update10 Beta D3D problems – 15x slowdown fixed||SproutCore – Apple MobileMe JS library »|