With Pentaho 5.0, the repository went from a file-based master repository to a database one. This has some advantages in that it’s typically easier to configure a single database in a clustered environment and point to that. However, it has the downside, that modification of text and XML files in the repository have a slower development cycle: edit, upload, test, repeat.
With the release of the Community Text Editor (CTE) that is no longer the case. You can edit, and test in a highly iterative manner. For example, I’ve been working on an action sequence (xaction) that’s in the repository. I simply open it up in CTE, edit, and run. I have the editor in one tab and the running action sequence in another. Change, test, change, test. Simple.
And lest you think it’s just a basic editor, think again. It has syntax highlighting, undo, and even cmd-S to save. It’s a very well done editor that I recommend any Pentaho developer have installed. Check it out in the marketplace.