Hi Chris,
I would suggest to go down another path, based on what ive found to be fast
in GWT and whats not:
Your performance issue seems to derive from two problems: first GWT RPC and
second single DOM manipulations.
To get your datastructures faster into the client I would suggest reading up
Thanks Jeff. I had thought of that idea, but then I'd somehow need to
tie in to the GWT event model so that I could capture when people
click on this text, firing through all my presenters and event bus. (I
just realised that I missed that bit off the first message).
Perhaps though that is fairly
I believe it would be trivial in that you would only need to add OnClick
event handlers for each of your divs. You would also have to refactor the
divs to be actual widgets such as Labels. If you are using UiBinder this
will be a piece of cake though if you aren't it is only slightly more
complex.
Performance is more acceptable when not in Dev mode, but for small
texts, we're looking at the browser hanging for 2-3 seconds while it
renders. Would be keen too, to understand why dev mode is so much
slower!
Chris
On Oct 30, 1:52 pm, Chris christopher.burr...@gmail.com wrote:
Hi All
I have
Setting inner text or html for each item will be very, very slow if done on
the client.
I'd generate all the items inside a parent container on the server in a
string and send that back to the client. Serializing the strong for
transport will be very quick.
On the client when you get the result
BTW, if the process to generate the content on the server were very
intensive and you wanted to minimize the impact of generating your content
on other users you could break the process up into smaller chunks or work by
making repetitive calls back to the server. How you'd coordinate these calls
