From: Jean-Julien Fleck Date: 2010-04-20T03:58:37+09:00 Subject: Re: Documenting Rakefile using rdoc Hello Eric, > If it could come in handy why isn't it documented with a desc? Because my boss does not wish to :o) > Hiding documentation behind a separate tool (rdoc-rake) that nobody knows about (just released yesterday) and mostly sucks (honestly, I only released it because you had an interest) is hostile to your users. What I would like to give to my (3) coworkers is a Rakefile (designed to handle book's compilation in LaTeX and ensure all the data needed to make the books have been gathered and up to date) and an online documentation (using your tool for which I'm very grateful). They would not have to compile the doc themselves. And the Rakefile has to be concise with the tasks descriptions because the very last person to use it (my boss) should be able to spot the right task to compile all the books at once in the right format (even if the editing process the intermediate tasks are very useful for us). I've documented all the tasks in the comments but opening the Rakefile to read them is quite tedious and not really productive enough. Knowing rdoc, I was just surprised nothing of the kind existed with Rakefiles, hence my questions. Could you tell me where I should look in order to modify a bit rdoc-rake to make it do what I want ? Cheers, -- JJ Fleck PCSI1 Lycée Kléber