It is also pretty good for Ruby on Rails coding, and getting better.
Ruby parsing is pain and a half, particularly for half-written Ruby code, but if you type something like
validates_(hit your autocompletion key)
in a controller you'll get a list of all the built in validations plus any you added which are in scope, and if you do something like
validates_acceptance_of (hit your autocompletion key) it will even tell you what all those wonderful damnable optional parameters are. It also saved my bacon once this weekend for
render :action => whatever, :layout => nil , which actually rendered the layout for quite some time until I backed out the "=> nil" and was told by autocomplete that what I really wanted was "=> false".
Netbeans is my favorite Ruby editor, much to my own surprise. One thing I don't like, though, is how much extraneous autocomplete information it provides. If I'm in a controller and type the name of a model object and then type period, it shows a dizzying dropdown list of thousands of methods, including several hundred different versions of the "new" method. Maybe it's just me.
Ruby parsing is pain and a half, particularly for half-written Ruby code, but if you type something like
validates_(hit your autocompletion key)
in a controller you'll get a list of all the built in validations plus any you added which are in scope, and if you do something like
validates_acceptance_of (hit your autocompletion key) it will even tell you what all those wonderful damnable optional parameters are. It also saved my bacon once this weekend for
render :action => whatever, :layout => nil , which actually rendered the layout for quite some time until I backed out the "=> nil" and was told by autocomplete that what I really wanted was "=> false".