Recent Posts by Geertjan Wielenga

I abandoned the scattershot approach I used in previous years and ended up focusing on a very small number of submissions. (Because last year I almost killed myself at JavaOne, after all 5 or 6 or so of my submissions got accepted, plus I had the most massive jetlag imaginable. On the upside, I watched all the movies that hadn't made it yet to the Czech Republic, at 3 AM on the hotel TV. The downside included almost falling asleep in the middle of my own BOF.) So, this year,...

Here's Part 9, building on top of Part 8 (which I will re-record soon), focusing on the Visual Library API: Duration: 18:05 // //]]> Supporting resources: Off-line viewing. Original link on NetBeans.tv. Transcript, more or less. There are many resources for learning about this particular API, on the NetBeans Platform Learning Trail: The whole series, of which this is part 9, is here: http://platform.netbeans.org/tutorials/nbm-10-top-apis.html

After a recap (hey, come on, it's been a long time since the last part, so I'm allowed to do a recap, ok), we dive into setting up a scenario for using the Visual Library API in part 9. So, here we see Nodes being constructed, as well as a first introduction to the Palette, constructed from our Nodes, with drag-and-drop functionality of our business object, represented by a Node, from the Palette into a TopComponent Duration: 36:10 The whole series, of which this is part 8, is...

The question of the day comes from "yueyue" (from the e-mail address), who [for some reason] wants to create a plugin that hides the Source Packages folder. Create a new module, call it "HiddenSrcPackages", with code name base "org.demo.hidden.src". Make sure to specify that you want a layer file (i.e., click "Generate XML Layer"). Then click Finish. In the Projects window, expand the Important Files node, then expand the XML Layer node, then expand "this layer in context". Scro...

I'm preparing for the final 3 parts in the "Top 10 NetBeans APIs" series. The main reason for the hold up has been that I seem to have lost the NBM file that installed my slide deck. :-( So I've basically given up on trying to find it. The series has already covered the majority of the APIs, the remaining three parts will consist of combining several of the APIs covered so far, plus there will be some interesting additions. Part 8 will end up with this scenario, after...

With everything moving to a server (a.k.a. "Cloud"), the question to ask is: "Is there still a role for desktop solutions?" I see three potential answers here: No! The Cloud has made the desktop irrelevant! Over time, less and less users will be found on the desktop. What's more, each second spent thinking about the desktop, and about frameworks for desktop development, is a second wasted. That wasted second should have been spent on thinking about the Cloud. Why is this blog...

I discovered today that the TopComponent for which you create a Palette must be an "editor" TopComponent. And here's the ultimate "Getting Started" for the world's simplest Palette: package org.node.sample;import java.util.List;import org.openide.nodes.AbstractNode;import org.openide.nodes.ChildFactory;import org.openide.nodes.Children;import org.openide.nodes.Node;public class NodeChildFactory extends ChildFactory<String> { @Override protected boolean createKeys(List...

The question of the day is by Brian Shepherd, who writes: My goal is to have the ability to add a new plugin that can add a node to the root node. i.e. Entity Manager EntityA EntityB ... EntityN Where each entity will be a different plugin and have the ablilty to add itself to the tree. That's a great question, which I provided the solution for in LookupListener & Children.Keys. The only difference is that, instead of setting the tooltip via plugins, we now need to set the...

The article I wrote on OSGi support in NetBeans IDE ended up on the java.net front page a few days ago: The cool thing about it is that I was able to use NetBeans IDE as a complete end to end development tool for extending GlassFish, using the same development paradigms as I do when creating NetBeans modules. Only the output was different (a JAR which is an OSGi bundle, instead of an NBM file). Really cool stuff. Another article on this topic that's really good is Integrating...