Thanks to everybody for sharing your opinion. I think there is a way to keep your project code and roo code side-by- side, as roo tries to keep the separation as tidy as possible through AspectJ, secluded packages, etc. I am not yet convinced, though, that keeping roo inside your project is necessarely a good thing.
It may happen that some Entities are just byproducts of a normalization process, and they just don't need Places, Activities, Views, etc. Additionally, in the (positive) attempt to avoid 3rd party crosscutting code, like spring IoC, guice or the like, you end up with roo using a lot of default stuff that you cannot easily replace (e.g. Activity.Display are not injected but are lazily built using a default view). Both GWT 2.1 and Spring Roo are pretty young, so we'll have to wait and see where they're headed. On Jun 24, 12:13 am, "Joseph Li" <[email protected]> wrote: > Think the whole point of having Roo + GWT is to easily generate pumping > codes like getters and settings and data transfer objects etc without too > much hand coding. I am not an expert on GWT nor Roo, but so far it looks > like it still need some work to iron out some strange issue, like the > generated scaffolding is not as robust as Grails and it doesn't run under > chrome but only runs on firefox. > > But as far as the concept goes and I am experimenting it hoping to recommend > it to our next project to use GWT + Roo. I love Roo keep monitor the state > of the project and generate mechanical code on the side away from the src > thru aspect so I don't have to do it and it won't mess my src up. It doesn't > bother me much that it’s a code generator. Grails is actually a runtime code > generator as well and it is very popular, albeit too much black magic and no > decent tool support. I say as long as it doesn't mess with my src, I am good > with it. > > Joseph > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of André Moraes > Sent: Saturday, June 19, 2010 11:37 AM > To: Google Web Toolkit > Subject: Re: GWT 2.1.0 M1 and Roo development lifecycle. What would you do? > > Jaroslav, > > I took a look in the Spring Roo videos and made a little notion on how > you it works. > > I wrote some programs when in college with the AspectJ (the base of > the Spring Roo) and it was very nice to have custom aspects around my > java classes. > > I think the main problem, at least for me, with the Roo tools is that > it works basically only for the Java Plataform. > > I don't found any links on how to use only GWT + Roo whithout any > server code. > > Anyway, i uploade some samples using my code template to generate some > GwtEvents (the base for the MVP cool development in GWT). > > Thanks for the links, maybe when in a only Java project I consider > using and learning more Spring Roo. > > On 18 jun, 19:27, Jaroslav Záruba <[email protected]> wrote: > > I don't dare teach anyone Roo, I'm yet to try it myself. :) Let me only > tell > > you that I'm having pretty similar concerns to yours whenever I hear "code > > generation". And after watching the video I know I will try it, it has > > impressed me enough. > > > 2010/6/19 André Moraes <[email protected]> > > > > Jaroslav, > > > > But how can I control the merge process? > > > In my case the code is generated, than i can edit make any changes in > > > the generated code (which will be preserved by the safe-code-marks) > > > and then the GWT compiler (or any other compiler) will compile the > > > code that i wrote. > > > > I don't really know/use Roo, but I used some code generation tools > > > before, so excuse me for any noob comment on the Roo subject. > > > > On 18 jun, 19:08, Jaroslav Záruba <[email protected]> wrote: > > > > 2010/6/18 André Moraes <[email protected]> > > > > > > I'm not using the integration with Roo, but I dislike the idea of > > > > > having a tool that after generating my code difficult to customize > the > > > > > generated code. > > > > > Roo keeps your code untouched. It stores the modifications elsewhere > and > > > > merges those files at compilation-time. > > > > -- > > > 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 > athttp://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.
