On Sat, Dec 30, 2006 at 04:42:45AM +0900, Hemant Kumar wrote:
> Mauricio Fernandez wrote:
> >rcodetools is a collection of Ruby code manipulation tools. It includes
> >xmpfilter and editor-independent Ruby development helper tools, as well as
> >emacs and vim interfaces.
> >
> >Currently, rcodetools comprises:
> > * xmpfilter: automagic Test::Unit assertions/RSpec expectations and code 
> >   annotations 
> > * rct-complete: 100% accurate (editor-independent) code completion
> > * rct-doc: document browsing and code navigator 
> > * rct-meth-args: precise method info (meta-programming aware) and TAGS
> >   generation
[...]
> Awesome work, has this been tested in Windows too?

Some people tried to use xmpfilter on win32 and there were some issues but I
believe they've been solved now (the code was modified so that it doesn't
require Kernel#fork/Open3::popen3 anymore, and some other problems were
addressed). If it doesn't work right now, I'm confident it can be fixed
easily, so just give it a try and we'll try to solve problems as they appear.

AFAIK the rct-* scripts haven't been tested on win32 yet (I haven't, and I
believe rubikitch doesn't normally do win32 either), but they are based on the
same code as xmpfilter so there's a good chance they'll work to some extent.

At the moment rcodetools ships with emacs/vim plugins that make them quite
convenient, but there's no reason why the same couldn't be done for other
editors. For instance, in vim <LocalLeader>r (\r by default) shows you the RI
documentation of the *actual* method being invoked, so if you have
  foo.dostuff
and several classes have a #dostuff instance method, it will determine which
definition has been used and show its documentation.

The vim plugin is in an early development stage, but rcodetools.el is much
more powerful and polished.

-- 
Mauricio Fernandez  -   http://eigenclass.org   -  singular Ruby