I believe the main goal of Activities/Places would be so that you don't have to write your own boilerplate MVP code. There is something to be said for writing less code. Any shiny objects that Google develops for that framework would also be at your disposal for free, and we all like shiny objects, especially free ones.
In addition, if it becomes widely adopted, it would also form a kind of standard layout for GWT apps. This would allow new developers to come into a project more quickly, and with a better grasp of where things should live in the application. -Ben On Jan 24, 3:49 pm, SergeZ <comp1...@gmail.com> wrote: > Ok, thanks to all of you! I agree that my first understanding of an > Activity stuff was wrong. But I still didn't discover the main goal of > them. What thing we can do with Activities (and Places ) that we can > not to do without them and using just EventBus, History and the MVP > pattern ? In my point the main goal of it is the possibility to make > the warning message when current activity stopes and the next one is > goint to start. Also, another benefit may be that we are about > writting less amount of code. What's more ? The official documentation > didn't help me to find the answer. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
