From: Peter Booth <pbooth@...>
Date: 2002-05-20T20:29:26+09:00
Subject: Re: [ANN] RubyEclipse released


Han,

three points:

Eclipse just may not be for you. I work in a team where approx 30% of
developers use Eclipse,
or its predecessor Visual Age, 40% use JBuilder, 30% use
vi,vim,emacs,slickedit,textpad.
All strong people who find they are happy/productive using different tools.

Eclipse has a steep, short learning curve compared to JBuilder - the payoff
took a week for me.

The Ruby plugin is version 0.0.1 - I suspect that its compelling only for
existing
Eclipse users.

Peter

"Han Holl" <han@pobox.com> wrote in message
news:3CE816C7.1060308@pobox.com...
> Adam Williams wrote:
>
> >4. Choose a file or a project and click on the Running Man button - This
> >will allow you to create a Launch Configuration. This is where you can
> >specify exactly which file to launch, interpreter and program arguments,
and
> >which interpreter to run with.
> >
> I guess you're using Windows. For it to work at all om Linux, I had to
> make a symlink
> ln -s ruby /usr/bin/rubyw.exe
> and then say that my interpreter was called ruby and lived in /usr.
>
> Then I got some output.
>
> But I must say (agreeing with James) that on first look eclipse is quite
> confusing. I don't like IDE's very much as a rule, the only one I use is
> JBuilder, and then only for the wonderful completion feature: you type
> System. and it pops up a list with all legal values.
> If such a feature is planned for RubyEclipse, I can swallow some of the
> pain. (Not being able to use nedit for instance is very painful when
> using the awful JBuilder editor).
> I think an extra problem for RubyEclipse is that every menu and button
> in it is loaded with Java stuff.
>
> For the time being, it's back to nedit for me.
>
> Cheers,
>
> Han Holl
>
>