Yes, I knew of the existence of QtRuby, but actually I think that the usage of the "QtRuby"-name in the QtRuby you pointed to is not justified. Usually QtXX is used where XX is something that is being made available in Qt. Language bindings start with the name in front, for example PythonQt, so it should be called RubyQt.
That's why I insisted on using the name QtRuby, well aware of the name clash.