On 2/4/07, Mark Ramm <[EMAIL PROTECTED]> wrote: > > > I'd like to hear the specifics of what you think needs attention in > the TurboGears Documentation. > > On my list for most important Documentation issue right now is the > fact that we haven't been successful in getting API docs generated by > PythonDoc, or Epydoc.
actually this is not entirely true I got a nice output out of epydoc the only thing that gave some trouble is widgets, all we need is to take action on this http://trac.turbogears.org/ticket/104#comment:11 which is better done on the server directly since it takes up a lot of space, which will be wasted on bandwidth. also I haven't taken down http://tg.maetico.com/api/ the next step here will be to delete the apigen folder from the root of the directory and replace it with a shellScript? that will run epydoc. Beyond that, I think we could use some good "orientation" > documentation which provides the big picture overview. Much like the > old Getting Started Guide did. > > And people always seem to need better Widget Documentation > > What else needs to be covered or covered better? > > -- > Mark Ramm-Christensen > email: mark at compoundthinking dot com > blog: www.compoundthinking.com/blog > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Docs" 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-docs?hl=en -~----------~----~----~----~------~----~------~--~---
