# Version 1.10.2 of Eclipse Code Formatter for Java introduces support for Workspace Mechanic and much more

In the last days and weeks I was busy enhancing the Eclipse Code Formatter plugin. The main focus was the support of the Workspace Mechanic [1] configuration file to be in compliance with my coworkers.

Offtopic: Workspace Mechanic is a plugin for Eclipse IDE itsself, which makes sure that shared Eclipse configurations are applied to your local installation. Have a look. It’s useful in a team of several developers.

Workspace Mechnanic also synchronizes the configuration of the formatter. Luckily its file format is quite simple and thus supportable by my plugin. So next to the standard XML-formatter file you can now use Workspace Mechanic EPF-files too.

I also added some other useful features you may like. That was the reason, why the release of this version took so long. For example now the “format on save”-action can optionally format the changed lines only. You can use formatter settings from .settings, you can configure the Java source level and the line feed. And the download size of the plugin has been massively decreased.

The full changelog can be found at [2]

In a few days it will be available as an update from within your NetBeans IDE. If you are curious and you don’t want to wait for it, then you can install it manually from [3] or [4].

Feel free to file issues and even better, provide pull-requests! We see us at NetBeans Day Germany in Munich on the 31st of March 2016. Get your ticket at [5]!

# Quicktip: Maven-based NBM development and the user-dir

When you develop a NetBeans module using the Maven-approach, every time you “Clean & build” your module the userdir, which is placed in the target-directory by default, will be deleted. “Clean & Build” is necessary if you’re altering the layer.xml directly or indirectly by using annotations like @ActionReferences.  So after that you have to reconfigure your target platform again, f.e. by opening the same projects and files to restore the previous state. That is annoying, but easy to fix.

<profile>
<id>userdir</id>
<properties>
<netbeans.userdir>../userdir</netbeans.userdir>
</properties>
</profile>


After that you can choose the profile from the profile-dropdown or in the context-menu of the project node.

This way the configured userdir is used for running/debugging your NetBeans module. It won’t get deleted automatically.

Advanced tips: Of course you can also configure an absolute path or even make the profile default by applying activeByDefault

<profile>
<id>userdir</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<netbeans.userdir>/home/user/myuserdir</netbeans.userdir>
</properties>
</profile>


# Quicktip: How to display your own Java code-templates in the code completion of NetBeans IDE

After blogged about How to display your own PHP code-templates in the code completion of NetBeans IDE a NetBeans user asked me how it works for Java code.

Yes, it is possible and it is even simpler. Since NetBeans 7.4 (issue #160771) you can define the context, where code-template has to be shown. Don’t be overwhelmed by the available contexts. For completions within a block/method choose BLOCK.

# Quicktip: How to display your own PHP code-templates in the code completion of NetBeans IDE

Here a small tip for all the PHP developers, which want to see their code-templates in the code-completion list of NetBeans IDE.

1. First create your own code template in code-template options at “Tools|Options|Editor|Code Templates” and save the options.
2. Then open the code-templates file from your NetBeans user dir. For example: c:\Users\johndoe\AppData\Roaming\NetBeans\8.0.2\config\Editors\text\x-php5\CodeTemplates\org-netbeans-modules-editor-settings-CustomCodeTemplates.xml This XML file contains all your custom template settings for the given mime-type.
3. Search for your entry and add contexts="php-code" to the <codetemplate>-tag and save it.

This way the template will be displayed in the code-completion list too.

When it looks like this

 <codetemplate abbreviation="ech" contexts="php-code">
    <code><![CDATA[echo "\${cursor} it works"]]></code>
 </codetemplate>

it will work like that.

If you like to have a option for that in the UI the NetBeans IDE itself, then please file an issue at https://netbeans.org/bugzilla -> Not needed anymore. See the update below.

UPDATE:  In the next version of NetBeans IDE (>8.1) no fiddling in files is needed anymore. Thanks to junichi11, who provided a patch to solve this via issue #246664 . The context can be set in the new context tab within the code-templates options.

# Code outline plugin 1.3.0 now supports dark themes

As you might already read in the NetBeans weekly newsletter, I also updated the Code outline plugin this week. This plugin shows the document content in miniature at the right gutter of the editor. Some of you know that feature from “Sublime Text” editor. This implementation is a bit simpler.

A highly requested feature was the support of dark themes. And now it’s supported. The basic text color and the background color of the editor is used. You can also check the “Darkening” option, which lowers the brightness of the code outside of the viewport. Try it!

Other improvements: You can define the font-size, but I propose to use single-digit font-sizes. The display quality has also been improved by applying anti-aliasing.

The plugin is already available from the plugin dialog within your NetBeans IDE 8+. Or it can by downloaded manually from the plugin page at [1] and github [2].

Please file issues/enhancement at [2]. I also like to merge your pull-requests for further improvements! Happy coding with NetBeans!

# New version of Eclipse Code Formatter for Java provides support for Eclipse 4.5.1 Mars.1 and @format:off

Within the last days I had time to update the formatter plugin, which allows you to format java source code using the formatter engine of Eclipse JDT. In a few days it will be available as an update from within your NetBeans IDE. If you are curious and you don’t want to wait for it, then you can install it manually from [1] or [2].

The major change is that the jars for the formatter engine are now taken from Eclipse 4.5.1 Mars.1.

As you might know, the plugin already provided support for @format:off before – if it was enabled in the formatter file. But now it provides some code templates, so that it easier to use. See the documentation at [3]

Feel free to file issues and provide pull-requests to see your enhancement in the next release! Happy coding and a happy new year!

# NB: How to create a context-aware submenu

Last time I blogged about “How create a context sensitive action with a submenu in the project-view?” [1].  Now there was an additional requirement to be fulfilled: The submenu should be only enabled, when exactly two project nodes are selected. Only if this condition is true, the submenu items should be displayed.

Thanks to the help of Jean-Marc Borer a solution can be provided too.

@ActionID(
category = "MyActions",
id = "de.markiewb.netbeans.sample.ContextAwarePopupAction"
)
@ActionRegistration(
displayName = "#CTL_ContextAwarePopupAction", lazy = false
)
@ActionReferences({
@ActionReference(path = "Projects/Actions")
})
public final class ContextAwarePopupAction extends AbstractAction implements ActionListener, Presenter.Popup {

private final Lookup.Result<Project> result;
private final transient LookupListener lookupListener;

public ContextAwarePopupAction() {
putValue(NAME, Bundle.CTL_ContextAwarePopupAction());
setEnabled(false);
//create an action, which is only enabled when exactly 2 projects are selected
result = Utilities.actionsGlobalContext().lookupResult(Project.class);
this.lookupListener = new LookupListener() {

@Override
public void resultChanged(LookupEvent ev) {
final Runnable runnable = new Runnable() {

@Override
public void run() {
int s = result.allInstances().size();
ContextAwarePopupAction.this.setEnabled(s == 2);
}
};
// to make sure that it will be executed on EDT
runnable.run();
} else {
SwingUtilities.invokeLater(runnable);
}
}
};
}

@Override
public void actionPerformed(ActionEvent e) {
//NOP
}

@Override