Introduction

WicketForge provides a number of useful features when crafting Wicket applications within IDEA. This page provides an overview of the more useful features.

Features

Inspections

Two inspections analyze markup and source files, informing you of any missing Wicket IDs.

Goto

Control+Clicking on a Wicket ID in the Java or markup takes you to the corresponding Wicket ID in the accompanying file. You may also toggle between the two files from the popup menu:

Completion

When editing a Wicket component class or markup, you may autocomplete component IDs and property values:

Autocompletion also works for Wicket XHTML tags:

...as well as PropertyModels as long as the IModel has a generic type defined:

Intentions

Intentions exist to create markup and properties files for Wicket pages and panels. To use these, click on the class name in the source file you're editing and the intention popup will appear:

Then select one of the available options.

Extracting Text to Properties Files

If you highlight text in a markup file, you can extract it to a properties file:

Selecting the option displays the Extract Text popup, where you can select which property file to insert the text or create a new one if it doesn't exist, as well as define the property key and value:

When finished, your selected text will be wrapped with wicket:message tags.