Ruber 0.0.10

Ruber is an IDE for the Ruby programming language written in Ruby itself and using the KDE 4 Ruby bindings.

It is plugin-based, so users can extend it adding the functionality they like. Being written in Ruby, plugins are very easy to create.

Installation instructions

- Install Ruby (http://www.ruby-lang.com). Ruber works with both ruby 1.8.7 and ruby 1.9.x

- Install RubyGems (note that ruby 1.9 already includes it)

- Install the KDE Ruby bindings (korundum) version 4.5.2 or greater

- as superuser, issue the command `gem install ruber` to download Ruber directly from rubygems.org or `gem install ruber-0.0.x.gem` if you downloaded it from here (note that gem will need to download other dependencies from the Internet).


Product's homepage

Requirements:

· Ruby
· RubyGems
· korundum

What's New in This Release: [ read full changelog ]

Features:

· Added a RI plugin. You can now insert the class or method name in the RI tool widget
· and see the documentation in a nice HTML format inside the tool widget itself.
· This plugin requires RDoc version 3.x (it isn't tested with version 2.x)

· Added an IRB plugin

· The syntax checker plugin has been rewritten. Now other plugins can check the
· syntax of a document

· Ruby and YAML syntax checker now are in their own plugin, rather than being part
· of the syntax checker plugin

· The auto end plugin doesn't use indentation anymore to decide whether the end keyword
· should be inserted or not. Instead, it performs a syntax check and only inserts
· end if ruby reports a missing end keyword. This should improve the accuracy of
· the plugin

· The Auto End plugin now inserts the end keyword after a case expression

· Clicking on a file name in an output widget with the middle mouse button now
· prevents the tool widget from being hidden, as if the pin button were clicked

· Changed the interface to specify patterns in the RSpec plugin

· The RSpec plugin now supports specs inside subdirectories. You can also specify
· subdirectories inside the pattern to match code file and the respective spec
· file

· When choosing the Run Specs for Current File action in the RSpec plugin, if the current
· document is associated with a code file, all the specs associated with it are
· run (previously, only one of them was run)

· When choosing the Run Current Spec action in the RSpec plugin, if the current
· document is a code file, the plugin will look at the most recently activated
· editor containing a spec file for the current file to determine which is the
· current spec

· The behaviour of output widgets when clicking on a file name which requires
· opening a new editor has changed. The choice made by the user to open the editor
· in the current tab by splitting the current editor is ignored if the current
· tab already contains more than one editor. The reason is that usually there
· won't be enough space on the sceen to comfortably accomodate more than two
· editors

Bug fixes:

· Do not crash when closing with unsaved files

· Horizontal scrollbar in the RSpec tool widget will be displayed when the spec
· description is larger than the widget but the rest of the text isn't