I haven't used any of the pre-packaged frameworks, so I can't help you select from them.
However, my team is using this architecture, having been inspired by the original talk at Google I/O. In my opinion, there is no better source of wisdom than that presentation, and its slides. If you haven't seen it yet, do so. If you've seen it less than 20 times, keep re-watching it day after day until you have. http://code.google.com/events/io/2009/sessions/GoogleWebToolkitBestPractices.html > I understand that GIN is used for dependency injection but not able to > understand Event bus, Presenter and Dispatcher as they are handled > differently by these examples.. EventBus is a decoupling mechanism, and is adequately explained by rjrjr in the video. "Dispatcher" is probably what rjrjr refers to as ActionService, which is an implementation of the "command pattern" for RPC. This is also discussed very well in the video. Presenter is the P in MVP, which is also discussed very well in the video. I suspect that after you have fully absorbed the presentation, you'll come back and look at the three samples/ frameworks with different eyes. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
