From: Lothar Scholz Date: 2005-06-07T16:50:14+09:00 Subject: Re: Could Ruby-doc be better? -- Proposal for a better system. Hello Premshree, PP> On 6/7/05, Andrew Thompson wrote: >> My basic plan is to have a php style manual >> http://www.php.net/manual/en/ generated from the rdoc comments, with the PP> I think it's easier for the PHP folks to have a manual like that, PP> because most (if not all) functions are pretty much built into the PP> language itself. With Ruby, we have a lot many libraries to take care PP> about -- consolidating documentation effort won't be that easy. Yes but the main problem is the bad implementation of RDOC which is not able to merge different "rdoc" runs into one "documentation repository". So if somebody want to spend time i think it's much better to do write a program that is using a good documentation database which allows addition and removal of documentation subtrees. Also everything gets more complicated with the open classes feature of ruby. So i don't think that a static manual is good enough. We must look 10 years ahead. And for the core and all c extensions i also think that the rdoc approach failed. I really like the way Lyle Johnson is doing rdoc handling for the FXRuby system, writing a separate documentation ruby file system. Look at the Tk binding or many other that are using the dynamic features of Ruby, they will never work well with RDOC and this is conceptionally. -- Best regards, emailto: scholz at scriptolutions dot com Lothar Scholz http://www.ruby-ide.com CTO Scriptolutions Ruby, PHP, Python IDE 's