From: Josh Cheek Date: 2011-08-06T15:52:28+09:00 Subject: Re: Brainstorming ideas how to improve Ruby's documentation --bcaec5015cff2de71604a9d0a8bc Content-Type: text/plain; charset=ISO-8859-1 On Fri, Aug 5, 2011 at 5:49 AM, Phillip Gawlowski wrote: > On Fri, Aug 5, 2011 at 10:48 AM, Marc Heiler > wrote: > > > > Once Rdoc is gone, start by making a TUTORIAL for the Ruby language that > > is MAINTAINED by the community. We live in the days of git and github, > > why shouldn't we all be able to maintain it on our own? > > I fail to see how an API documentation generator is related to > creating tutorials for a language. > > Thank you. I was becoming concerned with how many people seem to think they are the same thing. On Fri, Aug 5, 2011 at 5:54 AM, Fred L. wrote: > well, OK... forget it. my mistake. I use the forum interface and didn't > even think that it was a mailing list behind. > never understand why mailing list are used instead of forums.. whith > search/edit functions..etc. (and can't imagine how someone could > organize a mailbox with that. what if I add a mailing list incoming in > my mailbox for all of my interests... ouch..) > but forget it. back to the original post. sorry again. > > -- > Posted via http://www.ruby-forum.com/. > > I do that. I have gmail automatically tag them and remove them from my inbox. Then I just go check the tag every now and then, and see what's new. On Fri, Aug 5, 2011 at 7:47 AM, Keith Bennett wrote: > > I don't understand what you mean when you say "And totally unusable as well > by the way." -- how is it unusable? And how is the Pickaxe book ready for > retirement? It's an outstanding reference, and I'm often consulting it. > > I agree, I prefer the ruby-doc style docs (though I've never figured out why they list the files). And I also agree that the Pickaxe is probably the best Ruby book there is. I think they could do with removing the API that takes up a few hundred pages, but man, there is some _really_ great stuff in there. Not just API things, but intermediate things like how to structure your programs, and even extremely advanced things like how to wrap a C library with Ruby. I wish I had read it long before I did (I was put off by it's 1000 pages). --bcaec5015cff2de71604a9d0a8bc--