Why to use CodeEditor in Grails Applications?
March 31, 2009 at 9:28 pm Leave a comment
Currently, There are many perfect IDEs (Eclipse, IDEA, NetBeans) for groovy/grails project which has code completion, code refactoring, code formatting, syntax coloring and etc. So why developers need a tool like CodeEditor plugin?
- It has no setup step. It is a simple grails plugin. You can install it onto any grails application.
- It is accessible from web. You can work with CodeEditor in almost every browser.
- You don’t need to forward any ports except the HTTP port.
- You can edit a file and execute related actions with that file. For example if it is a controller you can reload controller and change the application behavior without reloading the whole application.
- You don’t need to download/upload your code to change.
- In many production environments accessing the server directly is not possible. CodeEditor enables users to access code without granting any access rights to server.
- You can control whole application from CodeEditor menus including reloading and applying current changes. Executing other commands which can be configured in grails-app/services/CodeEditorActionService.groovy.
- CodeEditor has code completion support. You can develop your code by the help of CodeEditor code completion suggestions easily. Currently, only groovy files has code completion support but I am planning to add gsp, javascript and xml code completion features.
In near feature I want to add go to declaration tool, code formatting and simple code refactoring support.
Advertisement
Entry filed under: CodeEditor, Grails, Projects. Tags: code, CodeEditor, ide, why to use.
Trackback this post | Subscribe to the comments via RSS Feed