Recent Posts by Geertjan Wielenga

I feel a little bit like that dude who invented the telephone. So, hurray, my Music NotePad works! My very first application built on the NetBeans Platform. Check it out—now, when you drop an item from the palette on the music sheet, the related note and duration are added to the editor. Same for the instruments—just click a button and the instrument is added to the editor. (Note that now there's a wider selection of instruments, made available by a scroll deal.) Then, when...

After stealing some cool graphics from the web, this is what my Music NotePad looks like now: I'm using the status bar for all communication with the user. Death to annoying JOptionPanes (and all their cousins)! For example, when the user drops an item too high above the music sheet, the status bar tells them about it and exactly what they should do to fix it. Same for when the item is dropped too far to the left. So, the user interface is basically finished. I reallyfocused...

I'm making a standalone rich-client application, instead of a NetBeans module. Makes more sense and is more fun—plus, NetBeans provides user interface support for just about everything, it even creates the application's executable for me. Here's how things look now (notice that most menus and all toolbars have been removed and that the small X on the top right-hand corner of the tab is also gone, because there's no need to ever close it): The drag and drop functionality works...

NetBeans is a slow learner. Doesn't spend sufficient time going through exercises. Seldom knows the difference between symphonies and concertos. Hearing Chopin, thinks it is Bach. Potential for future not so bright. However, first official music test shows promise. Is now able to distinguish one note from another. Or, at least, when pushed, is confident in locating the E: Maybe NetBeans will learn more over Easter break. Keeping fingers crossed.

Sometime ago I blogged about my first attempts at integrating the wonderful JFugue API into NetBeans IDE. At the time (click here), the user interface I implemented consisted of a new NetBeans window component for editing music strings (that the JFugue API converts to Midi files). All along, I've envisioned a music sheet on top of which notes are dragged from a component palette. Today I started working on that and here are the results thus far: What I'd like to happen, when...

I encountered a few problems since yesterday. First, for no reason I can determine, I suddenly wasn't able to use HTMLDataObject anymore. (I started getting messages saying that the org.netbeans.modules.html.HtmlDataObject couldn't be found. It might have something to do with the HTML module not being an API module, but that still doesn't explain why it first worked and then later didn't.) As a result, I couldn't check whether the current dataobject is an instance of HTMLDataO...

Wicket has a very specific scenario—each web page consists of two files, an HTML file and a Java file (I wonder how often I have blogged those words in this blog, must be at least two dozen times). Hence, chances are that you're working with both files simultaneously. For this reason, it would be handy if opening one of them meant opening the other as well. I gotta tell you—I was up until 2 a.m. this morning, working on this problem (which, for more experienced module...

This link in general: https://jax-ws.dev.java.net/jax-ws-ea3/docs/ This one in particular: http://wiki.java.net/bin/view/Javawsxml/JaxwsArticles

The problem with Wicket's Hello World! application is that it should be followed up by a simple quick start that extends the "Hello World!" scenario with two of Wicket's key concepts, both of which are initially quite tricky: Border and Panel. It's a good idea to understand both these concepts right from the start, i.e., right after "Hello World", because they powerfully illustrate two of Wicket's main driving forces: component reuse and consistency in look and feel. Panels...