Oops! How did that get sent???
I was wondering what advantages/disadvantages people had found. I
was thinking that the Wicket way might be more flexible with the mark-
up you can send? e.g. sending a list of items with background
images. I decided to stop being so lazy and look into it myself but
my computer thought otherwise and sent the email anyway!
But I am thinking about creating a version of the Wicket AutoComplete
that can use a global handler so that pages can still be stateless.
Any thoughts?
On 31 Oct 2007, at 07:37, Ryan Sonnek wrote:
don't forget about the scriptaculous autocomplete component as
well. It
allows for ajax/dynamic autocomplete, or using a static list of
results.
http://wicketstuff.org/confluence/display/STUFFWIKI/Script.aculo.us
+AutoCompleteBehavior
On 10/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
I want to use an auto complete component on stateless pages and in
theory there should not be a problem with this. Currently the
wicket
implementation uses the AJAX behaviour functionality which
...
waiting for the next episode :-)
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
