In this post I want to underline some of the big differences between the old and the new version.
First of all, the new Vorax was rewritten from scratch, taking into consideration the learnt lessons from implementing the previous version. Being a major version change, the API/commands are not the same anymore but, don't worry, because Vorax4 is supposed to have a more straightforward interface, and everything is covered into the Wiki or right into the Vim documentation bundled into the Vorax plugin.
The installation should be simpler. The ruby dependencies of Vorax can be now installed in one step using:
gem install voraxIn addition, Vorax4 supports Ruby 1.9 and Ruby 2.0. That's really a step forward since it's harder and harder to get Vorax running with the old Ruby 1.8 runtime on the new OS distributions.
As far as the Oracle documentation is concerned, Vorax4 doesn't depend anymore on external tools which must be installed on your computer, like it was the case with Vorax3 and Swish-e. Vorax4 relies now on the ferret gem which is automatically installed when you install the vorax gem.
Vorax4 is coming also with a better omni-completion system which should be smart enough to understand PL/SQL code too. This means that it'll also complete local variable names, types etc.
Another nice addition which wasn't in the old Vorax3 is the plsql code folding feature. Both these new features may prove to be a life saver for any PL/SQL Developer which is fool enough to code using the console only.
There's also a new output format called "pagezip", which compresses the output on a page basis, having the big advantage of spitting that page as soon as it gets compressed. This means that, unlike the "tablezip" format you'll have immediate feedback during the fetch phase. In addition, Vorax4 is smart enough to incrementally parse the output and to ask for any substitution variables or prompts, even in these custom output formats. This wasn't the case with the old Vorax3.
There are also some missing features, which were implemented in Vorax3 and get rid of them in Vorax4 for various reasons which I'm not going to cover here:
- no logging for the output window. You may decide, however, to save the output buffer as a regular file if you want to.
- no omni-completion for words within the output window. This can be achieved using the standard omni mechanism, but you have to configure it yourself if you need this kind of behavior.
- Cygwin support was dropped in Vorax4. It was a PITA to maintain it in Vorax3 with little benefit.
So, without further ado, I hope you'll like the new Vorax. It's still an Oracle IDE for geeks and you're welcome to contribute or to send your feedback.