Typically you would have a Presenter that initializes your view ( the static dom) , loads your view with data from an async server invocation , and receives requests from the view for more data . Have a look at https://developers.google.com/web-toolkit/articles/mvp-architecture-2.
Apart from dispatching url place requests via browser History, I personally hold off from using the event bus until I have a situation where multiple views may be interested in a single event or a given view is reused by many use cases with different presenters. The EventBus also is handy for managing a model cache (broadcasting model changes to interested views). Here's a recent video from last weeks Google IO : https://www.youtube.com/watch?v=kilmaSRq49g . The EventBus is covered about halfway in. David On Monday, May 20, 2013 8:15:22 AM UTC-4, Tim Hill wrote: > > Thanks Oliver, that has got me on the right track :) > > Next question... When I click on the save address button (for example), > the callback registers that the save button for address has been clicked > and runs the required method in the callback. This then calls an async > method in another class to save the address to a local SQLite instance. > What would be the best way to pass back the success/failure of the database > operation? Would it be on the eventbus, or is there a more preferred way? > > Sorry for the noddy questions, but still learning! > > Cheers > > Tim > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
