WorldTurner Blog

Google Analytics, Wicket and Panels

In this post I will go into ways to provide useful information to Google Analytics from your wicket components. For example, even if you stay on the same WebPage in wicket, you can still track the components on that page using Google Analytics.[Read More]

Posted at 03:16PM Aug 20, 2010 by Erwin Bolwidt in Wicket  |  Comments[1]

Refactoring wicket Pages to Components

Refactoring wicket Pages to Components We had an existing codebase that we wanted to refactor. It is an administrative GUI for a larger application with many different areas that need to be administered. The functionality was developed as wicket Pages, not Components. We wanted to integrate them in a tabbed user interface, and for that we wanted to use the TabbedPanel component from the wicket-extensions library. In this article I'll explain the steps we took to refactor this page-based application into a component-based application.[Read More]

Posted at 03:03PM Aug 20, 2010 by Erwin Bolwidt in Wicket  |  Comments[0]

Wicket best practices: Components vs Pages

Wicket has two kinds of building blocks for your applications: Components and Pages. Pages are top-level components, they exist by themselves and cannot be used as part of other Pages or Components. Components can be put on Pages or placed inside other Components. When you're developing using Wicket, you have to choose to make your own classes extend Page or Component. This post offers some insights in the pros and cons of each choice.[Read More]

Posted at 01:33PM Aug 20, 2010 by Erwin Bolwidt in Wicket  |  Comments[2]