On Fri, May 04, 2001 at 12:59:35AM +0900, Colin Steele wrote: > > It is my hope that the Ruby Cookbook (www.rubycookbook.org) might > serve as a home for precisely this sort of code - shortish snippets of > useful stuff that're too small for RAA, but not appropriate for RCR. I just took a second look at www.rubycookbook.org, since I knew to few of ruby when I visited first. Some thoughts: - Clicking on 'Eval Code' under a recipe brings up the message 'Your recipe doesn't have any Ruby code.' This should be 'Please log in to eval Ruby code.', just like when you click on 'Eval' in the navigation bar on the right side. - Apropos login: I do not like sites where I am forced to register and log in. I favor the Wiki approach where one can simple come and contribute. This is of course your decision. It might hinder growth. It might enhance security. I doubt that it improves security substantially. - Concerning Wiki: The separation of code and comments that is nice, but I would prefer if the Cookbook changed a little bit more into a Wiki. - First it should be possible to change the entries. For example if a recipe contains an error it should be corrected there, not in a comment like you had to do on TkTickTalk. - Second I would not put the code for followups on extra pages. It is too much toil having to click through them. Especially with the possibility to edit pages they should not get too long to justify splitting them up. - You should add a little warning on the homepage, that one cannot guarantee for the correctness or even harmlessness of the recipes. I saw the disclaimer in the TOS, but nobody really reads them. So something along Warning! The entries for the Ruby Cookbook are not moderated. So you should not rely on them as being correct. Some may even be harmful, smoke behind your back and steal your car. Understand them before you use them. should be nice to raise the attention for the problem. -- marko schulz Dieser Satz beinhalten drei Fehller.