Goal - Open Source Wicket Components

visural-wicket is a collection of Apache Wicket components and utilities. They are designed to be light-weight, loosely coupled and to be easily integrated into any existing Wicket application with minimal dependencies.

Each component is also designed to be easily customised to fit a particular system's requirements.

Other than components, visural-wicket includes some other utilities that assist in the development of Wicket applications, such as an annotation-based mounting system, model templates and automatic "form view mode" component.

Click here to see the features

Differentiation

How does visural-wicket differ from other libraries such as WiQuery? A core goal of this project is to provide components which do not come with a lot of dependencies. Something like WiQuery / JQuery UI are fine if you plan to use all of those components heavily, but many designers wish to pick and choose their tools and a mixture of custom and off the shelf tools for a more customised look and feel.

While visural-wicket uses JQuery (regular, not JQuery UI) for many of the components, as much as possible we've tried to keep the dependencies to a minimum, and clearly state them in the documentation.

Status/Roadmap

Here - Roadmap

Examples / Live Site

The visural-wicket-examples application is in SVN, and is available live here.

Discussion and Support

There is an associated Google Groups discussion forum.

Any bugs or issues should be raised using the issue tracker. Please search for an existing bug report before creating a new one.

Dependencies

visural-wicket is designed for use on JDK 1.6 with Apache Wicket 1.4 or Wicket 1.5.

There is a separate version of the current release for Wicket 1.4 and Wicket 1.5 respectively.

The only Javascript dependency is the JQuery Javascript framework, however not all of the visural-wicket components use JQuery. The ones that do are clearly marked as such. See the basic usage wiki for sample code for including JQuery in your project (we do not include it automatically).

The components have been tested on Internet Explorer 6,7,8, Firefox 3+, Chrome and Safari 4 without problems. (Note that IE6 may require some optional component features to be enabled - by default IE6 compatibility is disabled).