Archive for May, 2009

CodeEditor versioning support

When I made a CodeEditor demo to Berkay who is the director of the IFountain, he suggested me to add versioning support to CodeEditor.  At IFountain we develop integration tools for IT departments. The main tool we focused is RapidInsight. It is implemented on the top of Grails Framework with a lot of modifications. It has a lot dynamic features.  This is because of the variability of customer requirements. We are integrating with a lot of different systems and we need to create appropriate models and appropriate integration scripts for our customers. Actually, technical customers can do scripting and other integration modifications easily in RapidInsight but first they have to know Groovy little bit.

When we deployed RapidInsight to any production environment, we change the main product and modify models or some scripts according to customer needs (and of course we use CodeEditor to make these changes). However, after a short time changes applied to main product are forgotten. And if we want to rollback changes and return to any of previous point, we should remember all the changes we made. This is very error prone. If you can not remember a change, you may introduce a bug. The versioning support will help users in situations like this.

Some of the expected features of CodeEditor versioning system may be listed as:

  • Users will be able to edit the code freely, these changes will not be applied to working copy till they commit these changes.
  • When user commits the changes, they will be applied to main product
  • Multiple users will be able to edit same file at the same time. However, if any conflict occurs, it is their responsibility to resolve these conflicts
  • Users will be able to return back to any version. All of the changes applied to working copy will be rolled back.
  • Users will be able to customize versioning mechanism. A default implementation (File based or embedded versioning system) will be distributed with plugin and users will be able to customize from a file located under services directory.

All of these features, will make CodeEditor benefical for all Grails Application. I am planning to implement and release it with the next version of CodeEditor.

May 27, 2009 at 9:35 pm Leave a comment

CodeEditor 0.2.4 is Released!

CodeEditor 0.2.4 is released.

  • Several UI bugs are fixed and UI performance is improved (upgraded to EditArea )
  • Action execution mechanism and console view to see result of these actions is added. You can reload controllers/filters and etc after editing its content from CodeEditor ui. There are default actions and you can customize actions to be executed from services/CodeEditorActionService.groovy file. Actions will be visible in Exec combo box in toolbar according to configured context.
  • Default suggestion injection mechanism added to show dynamically injected methods in code completion. A default implementation is added you can customize and any method and property suggestion using conf/GroovyDefaultSuggestionConfig.groovy file
  • Gsp code completion support is added.

You can download it from Documentation of these features did not finished yet. I will write a detailed documentation soon.

Also, in the next version version control system support will be added. It will help users to manage changes in production environments.

May 27, 2009 at 10:39 am Leave a comment

CodeEditor 0.2.3 will be released soon!

I will release CodeEditor 0.2.3 soon. It has several major bug fixes related with UI and code completion feature. Also some major enhancements are implemented in release 0.2.3. You can see details from jira page

May 8, 2009 at 12:32 pm Leave a comment

My Twitter