CSS is a simple mechanism for adding style such as fonts, colors, and spacing to Web documents. This technology remains today confined to HTML and XML documents, although its principles are suitable for other domains. Let's see how we can use what we know to style Java objects, and then apply one typical styling system, Cascading Style Sheets (CSS), to the Java world to enhance the informative level of a user interface.
Most Swing components can be styled. However, the added value becomes more obvious as the components get more complex. This is why Table, Tree, and List are good candidates. An implementation of CSS for Java has been performed in ILOG JViews, a framework for displaying 2D graphics like charts, maps, and graphs. We will detail the advantage to use CSS engine with this framework.
Mathias Mouly has been a Technical Account Manager at ILOG for 7 years. He is currently in charge of the visualization product line in Europe. Prior to this, Mathias was involved with Thales in application development for EDF, the French electricity provider. Mathias graduated in energy engineering from the Ecole des Mines and in software computing from Thales campus.
blueMarine— In this talk we will show you the blueMarine project, an opensource desktop application to support the photographic workflow. blueMarine is being designed following the best practices for the creation of a 'filthy rich client', from animations to the use of JOGL, and taking advantage of the rich framework delivered by the NetBeans Rich Client Platform.
IRIS, a RIA swing applet— Iris shows the power of modern Java applets, highlighting the following major features of the Java platform: Dynamic extension of applets: new techniques developed within the past year in the JOGL project allow applets to use OpenGL for 3D graphics, OpenAL for spatialized audio, Java Media codecs, and other extensions previously only available to desktop or Java Web Start applications.
Spring is Swinging— Java is back on the desktop! We need to deliver high-quality, good-looking, multi-tier swing applications to our customers. How can Spring help us to achieve this at minimal cost?
Eclipse on Swing— Wouldn't it be great, if one had the choice between SWT and Swing not only at the beginning of a project but throughout development? How about using the familiar APIs to develop Eclipse-Plug-ins, RCP-applications or a JFace/SWT-GUI and still keep the option to switch back and forth between SWT and Swing without changes to your code?
JSR-296 Swing Application Framework— Well written Swing applications tend to have the same core elements for startup and shutdown, and for managing resources, actions, and session state. New applications create all of these core elements from scratch. Java SE does not provide any support for structuring applications, and this often leaves new developers feeling a bit adrift, particularly when they're contemplating building an application whose scale goes well beyond the examples provided in the SE documentation. This specification will (finally) fill that void by defining the basic structure of a Swing application. It will define a small set of extensible classes or "framework" that define infrastructure that's common to most desktop applications...
