Joe at CodeGear wrote:
My company, CodeGear (the Borland spin-off) has a survey open on Ruby
and Ruby on Rails. If you have two minutes we’d appreciate your input
on this survey.
The survey is at: href="http://www.surveymonkey.com/s.asp?
Briefly: Yes you should develop a Rails editor, and if it thinks
outside the box as much as Rails itself does, it could blow other
For example, most Rails development consists of adding a little to a
view, adding a little to a controller, then adding a little to a
model. So most editors follow the Rails directory format, and put the
models up here, the controllers all the way over there, and so on. The
ability to navigate smartly amongst stuff, without treating it as
separate files, would be priceless.
However, question 14 lists common problems with Rails development, and
you forgot to mention automated testing, or refactoring, in the list.
No editor should make that oversight.
http://c2.com/cgi/wiki?ZeekLand <-- NOT a blog!!