On Wed, 23 Oct 2002 15:54:08 +0900, JamesBritt wrote:
>> I have to be honest and say that I don't *get* why rubydoc *as a
>> tool* is necessary. If you're going to make it an aggregator so
>> that the user can have the equivalent of a single interface like
>> users of the ActiveState Perl package do ... that's cool. If
>> you're going to make it a super-duper version of ri with Rimport,
>> even better! (See? I forgot another Ruby documentation tool.) But
>> if it's just going to be Yet Another Documentation Tool, I've got
>> to say that I don't see the point.
> My goal with Rimport was to avoid inventing anything new, but
> rather to exploit what was already familiar and available. It's a
> bridge between RDoc and ri. Theoretically, it could be rewritten
> as a loadable output formatter for RDoc or as an XSLT
> transformation. Proof is left as an exercise for the reader.

Oh, don't get me wrong -- I haven't downloaded it yet, but I intend
to. The concept is perfect. The tool I forgot was ri, not Rimport (:

-austin
-- Austin Ziegler, austin / halostatue.ca on 2002.10.23 at 10.48.56