I am currently in a project where we do everything with jQuery in the
frontend, simulating Wicket's AJAX input and using its AJAX output.
However, I would not advice in doing this until you have a strong grasp
of Wicket's form and AJAX handling. Having a good jquery programmer
helps too.
Regards,
Erik.
On Thu, May 22, 2008 at 3:16 PM, Ned Collyer <[EMAIL PROTECTED]>
wrote:
Hi Edvin,
I am an advocate of JQuery :). I even won their icon design contest, and
I've been using it for years! I think it should be used in all projects
that require effects or cool DOM manipulation.
I love the "unobtrusive way" and xhtml strict!
That being said, when it comes to wicket AJAX - just use the wicket ajax
and
be done with it. No point mucking with something thats already
excellent.
It works and its easy. Why reimplement that bit - and potentially open
up
bugs that you need to go debug.
For effects and DOM manipulation, you can use JQuery by adding header
contributors. It is cleaner.. and in many instances easier to debug. It
makes development quick and painless.
If it wasn't wicket - id suggest using JQuery for ajax.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
