""" If all it takes to make a good post is to remind people that more/better documentation is needed, I just set up a daily reminder post and become poster-of-the-week for the next year or so. Because that is true for nearly every project alive, FOSS or commercial. """
Well, in contrast to his usual style, I think it was a pretty constructive post. That said, and with a reminder upfront that I really appreciate the hard work and labor of love that TurboGears devs have contributed, TG documentation definitely trails projects like RoR. I have worked with both, and though I had Python experience but no Ruby experience, I found RoR much easier to pick up, largely because, as Ilias pointed out, I could "go to" and not "search for". The API docs for RoR are great. With TG, it seems like I am forever fumbling around for a mini-howto on a wiki somewhere when what I need is reference documentation at a known location. The book, which I purchased as soon as it was available, is a great help. If I had that and good API reference docs, I'd be happy as a clam. (If I had "TurboGears in a Nutshell", along the lines of "Python in a Nutshell", I'd be in seventh heaven.) ;-) I truly hope that this does not come off like a whine because it is not intended to. But spades is spades and TG docs are presently behind the curve. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
