First of all, I would like to applaud the ROO team. Roo is truely a great addition to help bootstrap projects using Spring. I've been experimenting with it and am "sold" on it.
Second, as a long term builder of code generation tools, I can see both sides of this discussion. However, I strongly advocate providing means for viewing and editing the fully expanded code within the IDE. There are several reasons for my position:
1. In Roo's current state (I'm using RC2 and am about to try RC3) there seem to be many aspects (in the non-programming sense) that either don't work quite right, or at least create considerable sense of unease in the user. (Some of that unease and uncertainty may go away with the expanded RC3 doc - thank you.) One example is how does one go about using "field reference" or, more likely, "field set" to express a many-to-many relationship. Another example is that the use of "push-in refactoring" is still quite a mystery (I admit to being an AspectJ/ADJT newbie). Even after reading everying I could find on the topic, I could not get the Push-in refactoring options to show up in context menus (using either Eclipse with JEE (i.e. WST support) with ADJT 20 or with Spring STS 2.1.0).
2. Given the uncertaintity a new user of a new tool is likely to have (e.g. is the unexpected behavior due to bugs in the recently written code, have good when installing or configuring the tools, or am I simply misinterpreting the sparse documentation), it would be very reassuring to be able to see the generated Java code. While I can imagine what it would look like from reading the .aj files, seeing it all assembled would make extending that code easier sines a developer would know precisely what he is modifiying.
3. I am likely to need to add JPA annotations to the domain objects beyond what can be expressed in the roo "field" commands. Again, being able to see all the generated code would aid that process.
So I vote for making it easy to view the full generated code. And at the same time provide a way to retain my edits and still have roo act like that genie looking over my code to fix any inconsistencies I create.
Thanks again - Even in its present state, I can see that Roo is going to be a killer tool! Keep it up.