Recent Posts by Geertjan Wielenga

Spending some days in Prague for the first time in 6 months, then on to the next NetBeans Platform trainings. While in Prague, I got my new laptop (the old one kept sounding like a plane taking off) with, inevitably, Windows pre-installed. Haven't had the time to move to Ubuntu yet, so am reacquainting myself with the world of Windows. So far so good and NetBeans IDE 7.0 Beta 2 looks pretty sweet: Find all the related release info here: http://netbeans.org/community/releases/7...

A month from now I'll be in Boston, invited by the nice people from VisiTrend. VisiTrend provides tools and services enabling users to exploit their data, so that better decisions can be made through visual and interactive analytics. Here's the announcement on the VisiTrend site, note that anyone out there is invited to join in part of the time I'll be there: For details and contact info, go to the News section here on the VisiTrend page.

I now have a solution for co-ordinating JRadioButtons (and, as a consequence, JCheckBoxes and their related menu item equivalents, as well) in the NetBeans Platform toolbar. In the screenshot below, there are three radio buttons in the toolbar ("Zoom In", "Zoom Out", and "Pan"), which work as one might expect: I started by creating a separate class for co-ordinating the listening to changes in item state. I.e., whenever a different radio button is selected, existing listeners...

I'm working on a situation where, if no image panel is in the selection, i.e., because another window is selected, as below: The "Zoom In", "Zoom Out", and "Pan" checkboxes in the toolbar should be disabled, which is the case above. On the other hand, when, as is the case below, the window that contains the image panel is selected, the "Zoom In", "Zoom Out", and "Pan" checkboxes in the toolbar should be enabled, as can be seen below: The above, in itself, is a reasonably...

Yesterday was about "skinning" the NetBeans Platform main window. Today, let's look at runtime switching of look and feels: Whenever the user of the application mouses over a different button, the entire application is updated in terms of its look and feel. public class LAFSwitchButton extends JButton { public LAFSwitchButton(final String laf) { setText(laf); setPreferredSize(new Dimension(130,40)); addMouseListener(new MouseAdapter() { ...

While thinking about Henry's Nimbus challenges, I received a great tip from NetBeans Platform window system guru Stan Aubrecht: There's a small API change in openide.windows module (see version 6.38 in core-main repo) which allows you to make most of the main window components non-opaque (menu bar, toolbars, slide bars, status bar etc), so you can provide your own JFrame window to be used as the main window and have a custom painted background in that frame. The custom...

The NetBeans Platform session, though a "lightning talk" (i.e., 15 minutes) was pretty well attended (about 40 or 50 or so, in fact, I ran out of NetBeans Platform Refcards, so if you were there and didn't get one, drop me an e-mail or leave a comment here) at Jfokus yesterday. In that time, I did "The Hitchhiker's Guide to NetBeans RCP". I like that title, will use it a lot more. Given the limited time, after a very brief introduction, I ported the Anagram Game (with a few...

import com.vaadin.terminal.gwt.server.ApplicationServlet;import org.mortbay.jetty.Server;import org.mortbay.jetty.servlet.ServletHolder;import org.mortbay.jetty.webapp.WebAppContext;public class VaadinServletContext { public static void main(String[] args) throws Exception { Server server = new Server(8080); WebAppContext context = new WebAppContext(); context.setContextPath("/"); context.setResourceBase("./src"); ServletHolder...

You decide to predefine the size and position of the main window via the "WindowManager.wswmgr" file. One already exists in the "Window - Core" module, so you'll need to override that file. You create a new one and register it in your layer. Now, to ensure the correct load order of modules, you set a dependency on the "Window - Core" module. That dependency, since that module doesn't expose an API, needs to be an implementation dependency: All this is very inconvenient....