Welcome
Whats New
Features
Screenshots
FAQ
Documentation
Download
Contact
Frequently Asked Questions
-> Why aren't my output statements appearing?

If a user runs code such as:

puts "gimme your name:"
name = gets.chomp
puts "hello, #{name}"
You won't see the "gimme your name", before being prompted for input (name = gets.chomp) first. After the input, the two puts lines are printed out. This is a result of the way streams are handled.
There's a couple solutions. The first is to manually flush the stream after each put. The second is to set:
$stdout.sync = true
-> What language is RDT written in?

RDT is written almost entirely in Java. The Eclipse platform is Java based, and so writing plugins for it requires us to use Java. (Unless you're a smart cookie who can find a way to let us use ruby - perhaps JRuby?)

That being said, we do have some ruby scripts included in RDT to help us interface with your ruby code. A good example of this is the Test::Unit runner. The plugin actually communicates over a socket from a Java class to a ruby script. The ruby script handles the setup, running the test case and informing the Java runner about the status.

-> Which version of Eclipse should I install?

The RDT Development Team always aims to be compatible with the absolute latest version of Eclipse. The current release of RDT should be compatible with Eclipse 3.0+.
-> Which components of Eclipse do I need?

Generally speaking you should be able to download the Eclipse platform, without the JDT (unless you plan on doing Java development).
The download for Eclipse which includes only the platform (minus the plugin SDK and JDT) is typically labeled "Platform Runtime Binary". This the bare minimum you need to be able to run RDT. Obviously anyone with the full version including the SDK, or a version with the platform plus JDT should be able to RDT as well.