Roo project

Quote:

Originally Posted by spcmdr

Is there any some relation between your project and the one at skywayperspectives.org.

There is no official relationship between the Spring Roo project and Skyway Builder project. However, Skyway (the company behind Builder) is a partner of SpringSource (the company behind Roo). We believe Roo and Builder appeal to different target audiences, and both use different technical approaches to tackle the same problem domain of rapid Java application development.

Quote:

Originally Posted by spcmdr

Is there any official documentation?

Roo has an early-stage reference guide in its release ZIPs. This will be expanded considerably by the time Roo 1.0.0.GA is released in December. In the meantime we are publishing slides, blogs, videos and other resources as per the links in http://forum.springsource.org/showthread.php?t=71985.

Quote:

Originally Posted by spcmdr

There are some doc on the net like this video http://www.jroller.com/desmax/entry/roo. Is it possible to have the equivalent with an ide ?

You can download SpringSource Tool Suite and use Roo from entirely within the IDE. With STS you don't need to load Roo separately.

Quote:

Originally Posted by spcmdr

Sorry but I really hate command line and I am always surprise to ear that they are efficient. I suggest (I know it easy) something like this : http://orm.aquatool.org/nl/en/US/mod...eateTable.html. I like the way entities are been novelized (specially the table property with data type, java name, input)

Command lines can be horrible places if you've ever spent any time using poorly-designed command line interfaces. The problem with CLI design is you have to balance ease of learning, efficiency and expressiveness. It's really a case of "pick two", although for many systems you'd think they "picked none". :-) http://jonoscript.wordpress.com/2008...1-the-problem/ gives a great background on CLI design. I also recommend The Humane Interface by the late Jef Raskin, which is illustrative given Raskin's extensive background with the first Mac. A great shell if you'd like to see "Bash done right" (in my opinion) would be The Fish Shell, which is a wonderful *nix shell.

Anyhow, with ease of learning as a priority it's not too difficult to use the Roo shell. You just hit TAB all the time and it completes it for you. The hinting and command hiding also making it very logical to use. When in doubt type "hint". When a command isn't appropriate, you can't even see it in the lists when you hit TAB or type "help" (and certainly not "hint"). The Roo shell is one of those things you really need to just use to see that it's very easy.

One other really important point about the Roo shell is you do not need to use it. You can start your project using say "project com.foo" then "persistence setup..." and then quit the shell, "mvn eclipse:eclipse" and do everything else from within Eclipse. While in demos we tend to stay in the shell and/or write Roo scripts to record all the commands we've used (to make it easy to replay later), this is just our style as opposed to a Roo requirement. Roo was designed from the very beginning to sit alongside your IDE or text editor and if you prefer those environments they work extremely well with Roo.