Posts tagged as:

Example

Autocomplete with an Object

by sswinsburg on January 27, 2010

The Wicket Extensions package provides a neat component called the AutoCompleteTextField.
In a nutshell, this allows you to provide a TextField with a List of Strings and when you start typing, the ones that match the input show up. This is a great component, but consider this scenario:
You have a list of contacts, one of which [...]

Share this:
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • DZone
  • Slashdot
  • Technorati

{ 2 comments }

Enums internationalization with Wicket

by ildella on October 6, 2009

(Editor’s note: Olivier Croisier contributed this column from YesWicket.)
Enums are a convenient way to represent finite collections of elements : seasons, week days… As a consequence, they frequently need to be input or displayed in web applications – and it better be in a I18N-aware way.
Let’s see how easily Wicket can handle this.
Enums internationalization
Throughout this [...]

Share this:
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • DZone
  • Slashdot
  • Technorati

{ 2 comments }

A new step-by-step tutorial on how to integrate a Yahoo! User Interface Library (YUI) AutoComplete control with Wicket can be found here:
Wicket Tutorial: YUI AutoComplete using JSON and Ajax
It covers quite a few Wicket concepts, such as:

Creating a re-usable Wicket custom component
How to use a Wicket Ajax “Behavior”
Integrating a third party JavaScript widget into [...]

Share this:
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • DZone
  • Slashdot
  • Technorati

{ 0 comments }

We just finished up a little blog post talking about upgrading the sample app from 5 Days of Wicket to Wicket 1.4 which was just released. Learn about a simple conversion to 1.4 of MysticPaste.com on Mystic’s blog. We review some of our findings:

Generify everything for the most benefit
Deprecated classes now exist making [...]

Share this:
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • DZone
  • Slashdot
  • Technorati

{ 0 comments }