Is Spring Roo only for making the skeleton of a site?

Question

After many problems, I have finally set up Roo with a simple example.

Now I just want to know how far should one go with Roo.

I mean likes fields, classes, everything can be done through the Roo shell.

Now, for example, I have 15 classes in my project. I'm confused - to what point should I make classes with the Roo shell and when should I leave Roo and start working like normal?

Also, Roo has its own GUI and layout design. Can we change that also?

Answer 1

I personally use ROO to generate the models, controllers and the scaffold, then I strip out a large chunk of the Scaffold so that I can put my own components in there and some of the controllers I still need to write by hand. When you reach the point where you have an interface generated by ROO, start hacking away and only use ROO to add new domain models.