Originally posted by John Todd:
Hi.
How much it is easy to create Ajaxified components in Wicket?
Do I have the freedom to use any Ajax framework (jQuery, Prototype or DWR) for creating the components? or I have to following a blueprint?
I just remember how is painful to create Ajaxified JSF components, aooch.
Thanks.
It depends on what you call Ajaxified components. If you are talking about creating your own custom google map implementation from scratch it can be a challenge. However, if you plan on using Google map code and integrate with Google's javascript, it is not that hard.
If you want to make parts of your user interface Ajaxified, it is really simple. A lot of components already have an Ajax counterpart. For example Link has AjaxLink, AjaxFallbackLink (still works without Javascript), AjaxSubmitLink (submits a form). And if you want an Ajax indictator, you could use Wicket extension's IndicatingAjaxLink.
Section 1.3.2 from the
free first chapter of Wicket in Action shows how to modify the Link Counter example into an Ajax version.
Regarding integrating with other frameworks, Wicket uses its own Ajax framework for updating parts of a page by rerendering components and replacing the markup in the dom with the rendered markup. This makes it easy for non-javascript programmers to create Ajaxified UIs. But we are open to other frameworks, and you can see those efforts clearly in the
Wicket Stuff repository where integrations with jquery, scriptaculous, mootools and dojo exist.
