It can be done client side as a previous poster said using a timer with a
callback but first he should run Speed Tracer to determine why the code he
has now is bogging down the client.
Jeff
On Thu, Nov 18, 2010 at 12:23 PM, bjv wrote:
> On Nov 18, 8:09 am, MickeyR wrote:
> > Is there anything
On Nov 18, 8:09 am, MickeyR wrote:
> Is there anything similar to using java threads that I can use in my
> client side code ?
I can't think of any portable ways to do this. The only way you can
get the behavior you want that I can think of is to create a browser
plugin (like a firefox protocol h
If you really want to stick with the client side and want to have an
async-like experience you could also use a Timer to trigger the
search. Schedule the Timer as soon as the user begins to enter his
search and cancel + re-schedule it on every key hit. This way the
blocking search will only start a
I understand now & sorry for the confusion. It might actually be faster to
do an ajax call to do the look-up because it will be asynchronous and have
little impact on your ui. If for some reason you can't do that then use
SpeedTracer to analyze where you client side code is getting bogged down. It
Hi,
Traditional javascript (to which gwt java gets converted) architecture
is basically mono-thread in terms of real concurrent execution: so,
gwt has to stay mono-thread also.
The only possibility that I see to get muti-thread (in a standard
manner) with JS is HTML5 bu to my knowledge GWT doesn'
If you can target just HTML5, then you could use WebWorkers:
http://www.whatwg.org/specs/web-workers/current-work/
At the moment, you'll have to hand roll the JSNI to access them, but GWT
proper will be supporting HTML5 soon-ish.
On Thu, Nov 18, 2010 at 9:41 AM, MickeyR wrote:
> Sorry, I probab
Sorry, I probably was not clear. My entire story above is all
happening on the client-side.
So the search + display of results happens on the client, I'm not
making a RPC
to perform this.
Currently I don't want to make any part of this server-side, so any
idea on how to
achieve this ?
M.
--
You
Your ajax calls should be asynchronous so your client-side ui shouldn't be
slowed down by making the calls to the servlet to handle the lookup. Are you
sure you aren't making synchronous calls to the server? Also, use direct dom
manipulation over the widget supplied methods; get a widget's dom elem
Is there anything similar to using java threads that I can use in my
client side code ?
In my application a user types a search term into a Text box. For
every character typed in my code goes and searches in a dataset for
results containing the search string. These results are then returned
and di
