I am putting together documentation for my own project and will have another copy that is the same but intended to post to everyone. Below are some details on what I will be putting together over the next month. If anyone is interested in helping compile a good starting point that will be ready about the time of GWT 2.1 release, please feel free to contact me.
I will be giving a GWT seminar in late November at Carnegie Mellon to hopefully gauge the GWT interest and promote GWT-based development on CMU campus. I am keeping track of the changes going on with 2.1 development but may have some gaps here and there. I am fairly new to this type of development so if someone wanted to help out and fill in the gaps and make corrections where I go wrong that would be great Desktop Apps in the Browser w/GWT 2.1 Google-Web-Toolkit *Tuesday, November 30th (tentative) The power of AJAX Technologies when the Front-end complexity is abstracted Application Architecture Best Practices & Implementations - Model-View-Presenter (MVP) o Implementation using “Activities”, etc - EventBus & The Command Pattern - Dependency Injection (in client code) & The Factory Pattern - Data Synchronization using “RequestFactory” - History Management (Keeping the “Back” button) - Decoupling UI’s - DTO’s, Domains, & Databases - Foundation: o Java o Spring o Guice / Gin o Maven Outline: To-Do “Zero to Enterprise in 60 Minutes with GWT” (60 minutes may actually be 25 hours...) GWT is a compiler so you can build your app anyway you want and just have it compiled into a front-end/client application. However, this seminar is going to outline a few best practices as to how to structure and architect you application to take full advantage of GWT and provide very complex/large applications -Setting up your dev environment / getting started -High Lever Stuff -Lower level Implementation stuff -Appendix stuff that details out of scope topics and links/resources/ etc On Sep 30, 2:14 am, Daniel Kurka <[email protected]> wrote: > I'm sorry about the blog not being in english :) > > Thanks for the hint on SimplePanel. I`m gonna keep this in mind once m4 > arrives. > > 2010/9/30 Thomas Broyer <[email protected]> > > > > > > > On 30 sep, 00:18, Daniel Kurka <[email protected]> wrote: > > > I just started to take a look on GWT 2.1m3 and MVP and made a small blog > > > post about it. > > > > Maybe this will help? > > > >http://blog.daniel-kurka.de/2010/09/testdriving-gwt-mvp-from-gwt-21-m... > > > Could you please switch your blog to english? I was able to figure out > > what "Vorschau" means only because I've recently commented on other > > Blogger blogs. > > > Looking forward to read the next blog post! > > > (note that your SimpleDisplay won't be needed in 2.1m4 as SimplePanel > > implements AcceptsOneWidget –the new name for Activity.Display–; also, > > views generally will be widgets themselves, rather than contain > > widgets, again this is made a bit easier in 2.1m4 as Widget implements > > IsWidget, returning itself, so you don't have to write the asWidget > > method if your view is a Widget) > > > -- > > 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]<google-web-toolkit%2Bunsubs > > [email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. -- 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.
