YouTube: Overview of Newly Designed NetBeans Profiler

The redesign of the NetBeans Profiler is one of the big enhancements of the NetBeans IDE 8.1. In the release notes, you'll see a whole section dedicated to this:
  • Redesigned user interface
  • New features:
    • Live forward and reverse call trees in CPU results
    • Live allocation trees in Memory results
    • Monitoring CPU utilization
    • Thread dumps from profiled application
  • Engine improvements:
    • Faster connection to profiled application
    • Limited outgoing calls from profiled methods
    • Memory profiling for (more...)

New: Complete Guide to Tuning the Appearance of NetBeans

The full article is here and will be added to and updated over time and should be considered the most complete and authoritative document on the topic of tuning the appearance of NetBeans:

Kendo UI Core in NetBeans IDE 8.1

Good news for users of Kendo UI Core, everywhere. Problems in the initial release of the Kendo UI Core plugin have been fixed and, if you're using NetBeans IDE 8.1 Beta (or later), you'll have code completion for Kendo UI Core components, together with documentation, once the plugin is installed:

But... there's more! In code completion, in the place where you'd expect it, you also get code completion for the attributes of the currently (more...)

Hello Perforce in NetBeans IDE

Figured out how to add the Perforce item below:

How to do it:

Below is the starting point, in the layer.xml, included in the Git repo above:

<folder name="VersioningOptionsDialog">
    <file name="Perforce.instance">
        <attr name="instanceClass" stringvalue="org.netbeans.perforce.PerforceAdvancedOption"/>

The rest follows from there, see the Git repo above that contains the entry point for configuring Perforce in NetBeans IDE.

Related info:

Overriding Default Context-Sensitive Action Enablement

By default, when you create an Action that is context sensitive, via the New Action wizard, the NetBeans Platform looks out for the types that are of interest to you and, when they're in the Lookup, enables your Action. In the case below, when multiple Parts are in the Lookup, i.e., typically, multiple PartNodes are selected and their underlying Part objects are published, the Action will automatically be enabled:

        category  (more...)

Complex Properties Windows on the NetBeans Platform (Part 2)

In part 1, you ended up removing the UI components from the custom Properties window whenever the Lookup changes. That's kind of messy and here's an alternative approach, where you repopulate the custom Properties window instead of recreating its UI components.

public class PlanetPropertiesTopComponent extends TopComponent
        implements LookupListener {

    private Lookup.Result<PlanetNode> planetNodeResult;
    private final JPanel mainPanel;
    private boolean isInitialized = false;

    public PlanetPropertiesTopComponent() {
        setLayout(new BorderLayout());
        mainPanel = new JPanel(new MigLayout());