My experience with Roo was a bit overwhelming. The amount of code generated and the instant complexity was a lot for me transitioning from 1.x to 2.x style GWT programming. While the learning curve is hard and steep, building an MVP++ app from the ground up forced me to learn the details from the inside out.
I bookmarked a diagram posted on the gwt-contrib form that helped me visualize the Activities + Places/History mechanism. http://groups.google.com/group/google-web-toolkit-contributors/msg/7713e6c5d1bb5656 <http://groups.google.com/group/google-web-toolkit-contributors/msg/7713e6c5d1bb5656> http://tbroyer.posterous.com/ is a must read for understanding how to use the many parts of the frameworks. If you go with starting out small, the first step beyond building the sample application is to integrate Gin. Its essential to start early with DI because it impacts everything and integrating while the project is small saves a lot of rework. I also suggest sticking with building out the Place - Activity - View communication interfaces rather than customizing EventBus messages. Marshaling custom events and handlers adds a lot of complexity. The Place Controller and Request Factory are wonderful abstractions on top of the EventBus. After you've build a few CRUD panels by hand, you can really appreciate the help given by the Editor and CellList/Table frameworks although mastering them causes hair loss. On Wed, Jun 8, 2011 at 5:35 PM, Harry X <[email protected]> wrote: > Deanna Bonds <deanna.bonds@...> writes: > > > > > > > I was going through the same thing. I ended up going back and rewatching > the > Ray Ryan architecture videos from 2009 and 2010 again, but this time > drawing > down > all the diagrams, but combining them all. Then after having a big block > diagram > of the gwt framework and going the javadoc for the classes it just clicked > into > place. What I had problems with in the original readings of the docs, was > that > the overall big picture was really understated and somewhat confused by all > the > optional things. And an intended way(s) to use it combined with spring roo > would > help. That may be another piece of the puzzle for you. This framework > depends > a > bit on spring roo to generate all the boilerplate code. > > > > My way of using it has been to create a gwt project with the gpe. Then > add > spring roo to that project. Use Roo to create all the data enties, and > request > factories. At this point I'm guessing because here is where I am - let Roo > add > in > the client side mvp and simple uibinder display areas into it's special > generated > folder/packagePath. Copy the display areas into my own and modify them the > way > I > want and set up the places. Then add in backend logic. > > > > > > > > Thanks for sharing, Deanna. > Just tried 2.4 eclipse plugin and it creates client side MVP parts for you, > very convenient and good for me for now. Will check out Spring Roo. > > > -- > 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. > > -- -- A. Stevko =========== "If everything seems under control, you're just not going fast enough." M. Andretti -- 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.
