[ruby-talk:6183] Re: Minimal but practically useful Ruby browser?

"Conrad Schneiker/Austin/Contr/IBM" <[e-mail]> writes:

> What do you all think would be a "reasonably minimal" set of capabilities 
> for a Ruby browser (versus a full-fledged IDE) that would still be 
> practically sufficient for encouraging Ruby converts? Do you think there 
> could be any such thing?

I think that's a good question.

Many of the suggestions we've seen so far are wonderful, but might
have problems dealing with a dynamic language such as Ruby. Issues
include trivial things, such as how to represent singleton classes
such as

  def fred.doIt
  end

Do they appear on the class list?

So, I'd strongly support the idea of producing a small browser first,
and use that to experiment with various ideas before producing a
Visual Ruby++ or VA Ruby.

I was thinking: it probably wouldn't be hard to implement Ruby support 
for OOBR, the emacs-hosted OO browser. That might let us play around a 
bit. I'm not sure how many of the interested parties are emacs users
though.


Regards


Dave