Recent Posts by Geertjan Wielenga

Let's start here: <?xml version="1.0" encoding="utf-8" ?> <Graphic version="2.0" viewHeight="792" viewWidth="612" ai:appVersion="15.1.0.39" ATE:version="1.0.0" flm:version="1.0.0" d:using="" xmlns="http://ns.adobe.com/fxg/2008" xmlns:ATE="http://ns.adobe.com/ate/2009" xmlns:ai="http://ns.adobe.com/ai/2009" xmlns:d="http://ns.adobe.com/fxg/2008/dt" xmlns:flm="http://ns.adobe.com/flame/2008">     <Library/>    <Group ai:seqID="1" d:layerType="page" d:pageHeight="792"...

Always on NetBeans Platform courses we say "one of the advantages of modularity is that you end up with a clearer picture of the architecture of your application" and then someone in the group says "great, so how do I get to see that picture", and then I say "well, that picture is mostly in your mind since there's no actual tool to create that visualization graph and please feel free to go ahead and create one since you've now spent half a day learning about NetBeans APIs",...

When you press Alt-Shift-Up to move a selected piece of code upwards in the NetBeans Java Editor on Ubuntu, you'll find a clash of keyboard shortcuts with Ubuntu's own keyboard shortcuts. Thomas Kruse from the Munster JUG told me how to fix that:  sudo apt-get install compizconfig-settings-manager Start the settings manager by, for example, going to System -> Preferences -> CompizConfig Settings Manager. Then go to Window Management -> Scale -> Bindings and then rebind or disable...

Let's say you have this class: public class Customer { String type; public Customer() { } public String getType() { return type; } public void setType(String type) { this.type = type; }} Now, somewhere else in your application, you need to work with the Customer object. So, you create and initialize a new Customer, somewhere, and then later you want to call the getter on the customer. So you call up code completion (Ctrl-Space): Now, here are...

All along I've been doing Alt-Insert (which invokes "Insert Code") and going to "Generate Constructor..." and "Generate Getter and Setter...". I could have saved myself some time (i.e., several clicks in dialogs, etc), if I had realized earlier that code completion offers not only constructors but getters and setters too: Similarly, the overrides are also in code completion. Below, I'm in a Node, hence I see the Node overrides in code completion: Now I can just press Ctrl-Space...

I'm spending the weekend in India where I'm doing the NetBeans Platform Certified Training with a group of developers from JUG Chennai: There are a bunch of cool pics made from the 1st day of the course, including this one: After having given this course for literally several years, I've recently finally managed to put together a coherent story around the 3 use cases of Lookup, i.e., of loose coupling in the NetBeans Platform via the Lookup class: The image above shows all 3 use...

I'm encountering a problem for which there appears to be no solution. I even reimplemented the earlier prototype so that I now have no child nodes below the build.gradle, instead I have a Navigator showing the Gradle tasks, where you can click a task to run it. However, despite that, a crucial problem remains: whenever I run certain important method calls from the Gradle Tooling API... the NetBeans editor suddenly empties, not only for the current document, but for all...

So, the NetBeans/Gradle team has expanded over night by 1/3, now also including Robert Novotny. He provided the dependency resolution code, as well as the code for some nice templates (one for Java SE and one for Java EE), while Martin provided the code for calling Gradle tasks and for accessing the output, which is now integrated into the Output window. My part is mainly to handle the NetBeans IDE integration, which currently looks as follows: As you can see, the tasks...

Martin Skurla and I have a basic Gradle plugin working in NetBeans IDE: As you can see, ".gradle" files are recognized, are shown in the Projects window within a dedicated folder node, and are parsed to show Gradle tasks as children of the file node. Then, when "Run Gradle" action is invoked on a Gradle task node, which also happens when the Gradle task node is double-clicked, the related Gradle task is run, with output in the Output window. There's integration with the Groovy...