S
Stefano Crocco
Ruber 0.0.8 has been released today
Ruber web page: http://stcrocco.github.com/ruber
Ruber repository: http://github.com/stcrocco/ruber
CHANGES IN RUBER 0.0.8
New features:
* Added a new plugin: Auto End, which automatically inserts end keyword=
s after=20
module, class, if...=20
* Added a button to prevent clicking on a file in a tool widget to clos=
e it=20
while opening the file (replaces the use of the Meta key for the same s=
cope)*=20
Allow to open a new editor when clicking on a file name in a tool widge=
t with=20
the Meta key pressed
* Added horizontal scrollbars to the RSpec tool widget
* Unified Replaced Switch to File and Switch to Spec menu entries in th=
e=20
Ruby/Test menu
* Added an option to have the Switch to Spec menu entry create the edit=
orin=20
the current tab (by splitting the current editor), so you can have code=
and=20
spec side by side (mostly useful for people with widescreens)
* The Command plugin is now able to show output sent to standard output=
and=20
standard error
* Added menu entries (with the corresponding shortcuts) to move between=
split=20
views in the current pane
* Disabled autoscrolling in tool widgets if the scroll bar is not at th=
e end
Bug fixes:
* Fixed a crash when attempting to customize shortcuts
* Fixed a crash with nested views
FROM THE RUBER HOME PAGE:
Ruber is a fully modular IDE for ruby written in ruby using korundum,=20=
the KDE
ruby bindings which works on Linux (and should work on other Unix-like
systems)
Fully modular:
Except for the basic infrastructure, all of Ruber=E2=80=99s functionali=
ty is=20
provided
by plugins. This means that any user can easily augment Ruber=E2=80=99s=
features=20
by
writing his own plugin. He can also replace functionality provided by=20=
the
plugins coming with Ruber in a way which integrates seamlessly with=20
Ruber
itself.
Written in ruby:
Ruber is written in ruby, and so, of course, are its plugins. This mean=
s=20
that
its users already know the language needed to extend it. A very=20
different
situation from, for example, Netbeans where you=E2=80=99d need to learn=
Java to=20
write
a plugin for programming in ruby (in other aspects, Netbeans is a good=20=
IDE,
with very nice plugins for developing in ruby).
Using the KDE ruby bindings:
Ruber uses the wonderful KDE ruby bindings, which makes it expecially=20=
suitable
for people using a KDE desktop (but can be enjoied also by users with a=
different desktop). In particular, Ruber makes use of the excellent Kat=
e=20
part
for the editor window, meaning it has the extremely well-written ruby=20=
syntax
highlighter and most of the tools Kate itself has.
If you try it, please let me know what do you think.
Stefano
Ruber web page: http://stcrocco.github.com/ruber
Ruber repository: http://github.com/stcrocco/ruber
CHANGES IN RUBER 0.0.8
New features:
* Added a new plugin: Auto End, which automatically inserts end keyword=
s after=20
module, class, if...=20
* Added a button to prevent clicking on a file in a tool widget to clos=
e it=20
while opening the file (replaces the use of the Meta key for the same s=
cope)*=20
Allow to open a new editor when clicking on a file name in a tool widge=
t with=20
the Meta key pressed
* Added horizontal scrollbars to the RSpec tool widget
* Unified Replaced Switch to File and Switch to Spec menu entries in th=
e=20
Ruby/Test menu
* Added an option to have the Switch to Spec menu entry create the edit=
orin=20
the current tab (by splitting the current editor), so you can have code=
and=20
spec side by side (mostly useful for people with widescreens)
* The Command plugin is now able to show output sent to standard output=
and=20
standard error
* Added menu entries (with the corresponding shortcuts) to move between=
split=20
views in the current pane
* Disabled autoscrolling in tool widgets if the scroll bar is not at th=
e end
Bug fixes:
* Fixed a crash when attempting to customize shortcuts
* Fixed a crash with nested views
FROM THE RUBER HOME PAGE:
Ruber is a fully modular IDE for ruby written in ruby using korundum,=20=
the KDE
ruby bindings which works on Linux (and should work on other Unix-like
systems)
Fully modular:
Except for the basic infrastructure, all of Ruber=E2=80=99s functionali=
ty is=20
provided
by plugins. This means that any user can easily augment Ruber=E2=80=99s=
features=20
by
writing his own plugin. He can also replace functionality provided by=20=
the
plugins coming with Ruber in a way which integrates seamlessly with=20
Ruber
itself.
Written in ruby:
Ruber is written in ruby, and so, of course, are its plugins. This mean=
s=20
that
its users already know the language needed to extend it. A very=20
different
situation from, for example, Netbeans where you=E2=80=99d need to learn=
Java to=20
write
a plugin for programming in ruby (in other aspects, Netbeans is a good=20=
IDE,
with very nice plugins for developing in ruby).
Using the KDE ruby bindings:
Ruber uses the wonderful KDE ruby bindings, which makes it expecially=20=
suitable
for people using a KDE desktop (but can be enjoied also by users with a=
different desktop). In particular, Ruber makes use of the excellent Kat=
e=20
part
for the editor window, meaning it has the extremely well-written ruby=20=
syntax
highlighter and most of the tools Kate itself has.
If you try it, please let me know what do you think.
Stefano