Ben Giddings wrote:
> Laurent Julliard wrote:
> 
>> - Testing, testing, testing...: testers are
>> badly needed. By testers I mean people that use FreeRIDE but are also
>> willing to identify the root cause of a bug and fix it. I use FreeRIDE
>> myself for FreeRIDE development but I tend to always do the same
>> operations which is not o good way of testing.
> 
> 
> Ok, I use Emacs with ruby-mode.  I've looked at FreeRIDE before, but I'm 
> not sure what there is there that would make me want to use it instead 
> of Emacs.
> 

Integrated debugger and script runner, easy to navigate Class 
browser... and soon (in 0.9.4) the integrated Ruby documentation which 
will allow you to get instant help on any class or method definition 
you are typing in the editor. I am already addicted to it... :-)

Collaborative programming is also something that we have on our radar 
but nobody has taken over this task for now. it's a shame because that 
   is really an exciting one that I have not seen in anyother IDE 
(ruby or not) so far.

> You might get more people to help out with testing if you could provide 
> some compelling reasons why they should use FreeRIDE.  Even if those 
> features are, as yet, over the horizon.  If I knew I could have a Ruby 
> editor with all the keystrokes of Emacs, but customizable in Ruby 
> instead of lisp, I'd jump in a second... but it doesn't look like that's 
> what FreeRIDE is, or what it aims to be.
> 

If only I had more contributors to FreeRIDE, customizable key-bindings 
would have been done long ago. There is however a limitation in the 
Scintilla editor that command keys can only be one key. Emacs uses a 
lot of double key commands which Scintilla does not support.

Want to join and make a difference ?

Laurent