Follow up on this matter.
Thanks you for all the inputs, we considered them and decided what is the
best solution for our project.
In the end we created an object that models the data that we receive from
the database and from the after calculations.
In the HomeActivity class of the HomeView (in
Hei there,
I have a general wondering about the architecture of GWT applications.
Currently we have a web application which grabs some data from the
database, makes some calculations and then displays it on the GUI.
Sounds easy cheesy still because GWT works with RPC and eventbus I can't
Timea,
Not sure what the implementation trouble is:
1. User makes some interaction (i.e. button click) so you fire and event
(i.e. ShowSomethingEvent(id))
2. A listener sees the event and fires and RPC with the data from the
event
3. On returning the async handler for the call
If you have multiple independent RPC requests and you want to update the
GUI after all these RPC requests are done, then you could check a number of
boolean variables (one per RPC request) to see if all of them are true ( =
RPC is done), e.g.
server.rpcMethod1(Callback() {
onSuccess() {
To use BatchCommand you can use
gwt-dispatch.https://code.google.com/p/gwt-dispatch/
2013/6/11 Jens jens.nehlme...@gmail.com
If you have multiple independent RPC requests and you want to update the
GUI after all these RPC requests are done, then you could check a number of
boolean variables
And since the last sentence of the original post if my memory serves me right
mentions is for a mobile app I would strongly recommend not to use gwt-rpc in
this case.
Sent from my iPhone
On Jun 11, 2013, at 3:24 PM, Jens jens.nehlme...@gmail.com wrote:
If you have multiple independent RPC
Thank you for the so far posted replies.
For maybe further clarify:
- I need this to work only at the start up of the application, to wait
till my model has all the data and then update the GUI.
- I am using mGWT, still the architecture is GWT related. I am using
mGWT to get it
@Timea RequestBuilder or RequestFactory.
If you plan on creating a Mobile Web App you can def. look at GWT-RPC.
However, if you plan on packaging the App to Native as part of the dual
mode (web-native), then avoid if possible GWT-RPC.
Regards,
Alfredo
On Tue, Jun 11, 2013 at 3:41 PM, Imy
Timea,
If you've got the case of waiting on a multiplicity of RPC's to complete
before continuing, something like Jen's suggestion is best. I've
implemented it before with a multibit latches.
However you get into the issue of syncing. For example, let's say you have
N RPC calls for a given
