Thanks for you suggestion.
Not sure that would be enough. This is my use case:
- I have 3d applet in my view, it takes a while to load, as well with
user authorisation, etc... I am able to detect when the applet has
started running though
- the view is created once and managed by client factory
- my activity loads at start up some user data, some of it to be
displayed in the applet via my view interface
- I need to be able to wait for the applet to be ready to add the user
data, at least for the first time the view has been created
This is actually just as valid for the 2d map, which I load
asynchronously via the google api library. Even if I didn't I still
need to be able to habdle the case where the library hasn't loaded at
all, reached api limit or network issue, and prevent the activity from
trying to add map data.
My current idea is to add a whenViewReady(AsyncCallback) to my view in
the activity start. This method will call the callback if the view is
already ready (immediate) or when the view is ready (upon completion
of the load). If there are better suggestions (use of event bus or
else), I am happy to hear them.
Thanks for any help,
Thomas
On Feb 3, 1:06 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> Simply wait for all your code to be "loaded" (could be required scripts, or
> RPC/RequestFactory calls to the server) before "pushing" your view into the
> AcceptsOneWidget passed to the Activity#start() method.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment