Hello, Today I did some tests trying to document Freevo codebase using EpyDoc. Although it doesn't have the fancy and polishment that DoxyGen have, specially the nice dot graph library that generates cool hierarchy graphs, it works quite right (well, it fails to understand some unicode chars from src/tv/xmltv.py, but we can work around that).
So I want to know from other developers: Do you want to start documenting Freevo using a tool like that? Doing so can help us with documentation, a pain in the @$$ as everybody knows. Also, it can force us to better document the code. If we vote so, we need to also agree how to maintain these docs, maybe it's better to have it in CVS too (maybe another module) and someone be responible to run it every week or so and check everything is ok, otherwise fix/mail the changes author to fix it. also, a block diagram relating modules would be cool... if somebody knows something that does that for python code, please say. Otherwise a simple hand-made diagram would help... it would not require "that" maintance, just when fundamental changes were made, IE: the new plugin structure, etc... Gustavo _______________________________________________________________________ Desafio AntiZona: participe do jogo de perguntas e respostas que vai dar um Renault Clio, computadores, c�meras digitais, videogames e muito mais! www.cade.com.br/antizona ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
