From: Rich Kilmer <rich@...>
Date: 2001-12-31T16:42:42+09:00
Subject: [ruby-talk:29823] Re: FXRuby FreeRIDE Spike uploaded.



> -----Original Message-----
> From: Curt Hibbs [mailto:curt@hibbs.com]
> Sent: Monday, December 31, 2001 2:25 AM
> To: ruby-talk ML
> Subject: [ruby-talk:29822] Re: FXRuby FreeRIDE Spike uploaded.
>
>
> > From: Phlip [mailto:phlip_cpp@yahoo.com]
> > Sent: Sunday, December 30, 2001 9:42 PM
> > My RUedit concept, based on UEdit...
> > The editor provided primitives and between >every< command and the
> > primitives is a bit of script, no matter how short, written >inside< the
> > editor.
>
> I really like this. It truly enables rapid incremental development. There
> should be an integral way to package up and submit such additions to the
> project for inclusion in the distribution.
>

I like this as well...I've always thought that the power of a pure-Ruby IDE
would be its ability to be scripted (dynamically) in Ruby.

[snip]

>
> Have you used IntelliJ IDEA? Its a java with very good
> refactoring and code
> navigation features (http://www.intellij.com/idea/). I want FreeRIDE to
> eventually match this level of support for Ruby development. Being able to
> parse Ruby and knowing where you are in the syntax tree will be essential
> for this as well as simpler stuff like syntax highlighting.
>
> I like the idea of an all Ruby implementation, including the editor. If we
> had insufficient developer resources, I would prefer to go with something
> like scintilla. But having someone like yourself to champion the
> editor-in-ruby approach would easily change that.

I think that the text editing component should NOT be in pure Ruby.  A
rich-text editing component is extremely complex and responsiveness should
be a big focus.  I remember the original pure-Java components...they were
REALLY slow and got in the way.  As long as the editing component has a
sophisticated enough API and that API was completely wrapped by Ruby calls
(like I did with Scintilla) I think it gives you the best of both worlds.
Remember, you are always going to be tied to some toolkit for a GUI in Ruby.

- Rich