thx for the info jens,
do you say there is no way to keep the browser responsive but to do less
work/ transfer less data on/to client? is there at least a way to keep
browser responsive if browser has to do much work/logic?
if i understood it right: transfer much data is worse than to do much
it's an tree with 16k items (all administrative units of germany) - the
main advantage to load all items is, i got a very fast live search on the
tree. but as i said before i don't want to discuss this here. i ask how to
get an loading overlay/progress bar that doesn't freeze on loading.
i saw
If you load that 16k items with GWT-RPC your first problem that freezes
your browser is probably the deserialization process when receiving the
answer from the server (converting the string received back to your object
graph / list). So comment out all your tree stuff and first solve the
At the start of my App the Browser has to load some stuff and create some
data objects (Trees). The Problem is, that this blocks the the whole
browser (no tab switching no reaction on user interactions, even my
animated loading.gif is not loaded/animated). In swing applications the is
a
Javascript is single threaded, so you shouldn't do too much in one go.
You can use Scheduler.get().scheduleIncremental(repeatingCmd) to do some work
in pieces. If the problem is that it's slow while dealing with large RPC
messages, then you may need smaller messages.
HTH
Paul
On 02/11/11
thx,
are there any examples how to use scheduleIncremental? I don't want/can't
to split the work that has to be done manually but i want to give the
browser a chance to do other stuff - is it possible to interrupt a task for
some time?
In my case the main work has two parts: loading of data
Sounds like you're creating a tree with too many items. (How many?)
Maybe you need some lazy creating of tree items.
Paul
On 02/11/11 11:27, tanteanni wrote:
thx,
are there any examples how to use scheduleIncremental? I don't want/can't to
split the work that has to be done manually but i
