János Cserép has created a Wicket based portal in Hungarian. I can’t remember seeing him on our mailinglists, but it looks great, and is probably the first Wicket 1.2 application in production and externally visible.
Now if I only get some time to pick up my hungarian lessons. Szia!
Igor Vaynberg, (not his 2.0 reincarnation) has asked for help in Wicket’s quest for a decent Javascript date picker that works with i18n and SimpleDateFormat patterns. He writes:
as you guys know weve been having a lot of trouble with the datepicker in extensions. a lot of it is from the issues of i18n and formatting in general.
i started working on a replacement keeping those two items on the top of the list. the idea is to be able to define locale strings as well as a format expression that will be used for formatting and parsing and are identical to the ones used by SimpleDateFormat in java.
when all is said and done it might look something like this:
new DatePickerField(id, model, "EEEE, MMMM d yyyy")and have localized properties like
wicket.datepicker.months=January ,February... wicket.datepicker.shortMonths=Jan,Feb,... etcso the transition between java and javascript will be seamless
i also want to be able to decorate any day square via ajax or another mechanism
So if you are interested in building a killer Javascript calendar that works with existing Java idioms, give us a call.
I just committed an Ajax Wicket component for rating stuff, similar to the Votio wordpress plugin.
The links are rendered as Ajax links, which also provide a fallback in case Ajax isn’t available. This way the vote almost always gets through. The component renders itself when the ajax request returns, and as a component user, you can also update other components yourself in the same request.
Adding the rating component should be as simple as:
Rating ratingModel = new Rating();
add(new RatingPanel("rating", new PropertyModel(ratingModel, "rating"), 5))
{
protected boolean onIsStarActive(int star)
{
return ((RatingModel)getModelObject()).isActive(star);
}
protected void onRated(int rating, AjaxRequestTarget target)
{
((RatingModel)getModelObject()).addRating(rating);
}
});
and in your markup all you have to do is:
where you want your rating box to go.
All you have to supply is your own implementation of a Rating object, which will keep track of the number of votes, averages the votes, and creates a rating.
Features of the rating component:
The component will be part of wicket-extensions-1.2.1 (the next maintenance release of Wicket).
It has come to the conclusion: we’ve finally released Wicket 1.2. It took some very long hours and hard working days: blood, sweat and tears were spilled, babies were born (congratulations Igor!) and hell froze over.
This release is a major landmark in the (short) history of the Wicket project. I’ve blogged several times when we released the release candidates, so you may already be familiar with the new and improved list:
Spring support for injecting your business logic
into your web pages in a non-intrusive manner,
while still being able to use the convenient
Wicket idiom for creating pages (using the Java
new
operator).
Wicket runs on any application server supporting the servlet
API version 2.3 and higher, and will work on Java 1.4 SDK’s
or newer.
We have tried to keep API changes to a minimum, but had to change and remove some methods and classes. Wicket 1.2 will not be a drop-in replacement, though most of your application’s pages and components should not be affected. There is a migration guide available on our wiki:
The Wicket 1.2 release is a highly anticipated major landmark in the history of Wicket. The core development team wishes to extend their gratitude to all users who helped build and test this release.
Enjoy and have fun!