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 really know when each event is ready to fill the GUI completely. My ideea that I saw in some projects is to define States of the application(using state pattern). In the initial state I wait for the data from the DB and I wait also for the calculations and when my data model is complete I change the state and display it on the GUI. Do you think this is a valid way or are GWT applications designed differently? I want to also mention that it is a mobile application so response time is also important.
Cheers, Timea -- 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.
