What are the ’Killer’ Features For A Ruby On Rails IDE?
Please only leave comments relating directly to this article.
Do not leave technical questions or general questions.
If you have any technical questions, we request that you join the forum in order to post them: http://www.sapphiresteel.com/forum/
Rails is difficult to do because a) Rails is a pig to parse for IntelliSense: very, very dynamic! and b) Rails relies on ’context’ - i.e. where the files are in relation to each other and what they are called. Still, I think AR is doable, so I’ll have a go at that.
Tail - that’s a nice idea. I’ll have a think about it. I can’t see any technical reason why it cant be done.
Character glyphs: that’s tricky. The real problem is that Ruby is essentially ASCII + a few not very good hacks for Japanese characters. It isn’t Unicode by any stretch - that’s supposedly coming in Ruby 2, from what I remember. It might be doable via a custom Encoding class, but I can’t think of an easy way to preserve the spacing. A real ’>=’ glyph would only take up one space while in the underlying file, it would take up two positions. It would be very difficult to maintain a map for say, error reporting.
Dermot