[EMAIL PROTECTED] schrieb: > The tool Ian mentioned is here: > http://svn.berlios.de/svnroot/repos/docutils/trunk/sandbox/py-rest-doc/ > (following the discussion on > http://mail.python.org/pipermail/python-dev/2007-May/073259.html) > > It's a DOC generation tool but not an API generation tool. > So it may not suite for our API generation case.
And if we were to think about any other (non-API) documentation tool (not that I think that we should) we must think about a way to migrate what's already in the wiki. Unless we want to start docs for 1.1/2.0 totally from scratch. IMHO any technical solution can only take the pain out of the documentation effort so much. In the end, you just have set some time aside and *write that documentation*. Regarding the API-doc generation, I second Noah's sentiment. Don't get to fancy, choose a tool, that produces a usable output and when you've got that working *then* you can think about improving it. Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
