Hi Mindaugas, I don't know it very deeply, just stumbled upon it accidentally while reading about Python 3.0. The end result looks very clean, just like the doc sources (even cleaner than MediaWiki, if such comparison makes any sense). So Harbour came instantly in mind. It doesn't seem like a source code scanner though, so the docs has to be converted from some format (like NG) or written from scratch. Since the format is simple, conversion may be feasible.
I agree that neither Robodoc nor Doxygen is perfect for Harbour, so this one may still have a chance. hbmake is useless as is. We should dump it sooner or later, otherwise we will stay under the false impression we have a working documenter tool ;) Docs would indeed be important for Harbour. I wish we could somehow borrow the xhb one, or cooperate with xhb to make it apply for both projects. This way it's a proper waste of resources. BTW, Python is a beautifully crafted tool, and certain issues and development directions seem to fall in line with Harbour's. Brgds, Viktor On Wed, Jan 14, 2009 at 6:48 PM, Mindaugas Kavaliauskas <dbto...@dbtopas.lt>wrote: > Hi, > > > http://sphinx.pocoo.org/ >> - Documentation format >> > > Viktor, can you add some comment about this documentation system. Does > Sphinx parses source files? Can it parse .prg code? > > I'm used to see to sources, but sometimes it would be more quick to look to > docs for function parameters, etc. I've looked to utils/hbdoc, but could not > make anything, because hbdoc.exe requires some Norton Guide link file, I was > not able to find one in SVN. > > > I've also tried to look at a few documentation systems: > 1) Robodoc creates manual using ugly "section/subsection" headings. > 2) Doxygen is oriented to object oriented programming style. It tries to > document classes, methods, etc., but no documentation for functions. Though, > I was able to manage documentation of functions by including it into > modules. > Doxygen analyses code itself (not only documentation inside comments), so, > it is unable to parse unsupported programming language (i.e. PRG code). > > > Writing a simple source parser (parses documentation tags inside comments), > it's a few hours job. I think we need one for function documentation. > > > > Best regards, > Mindaugas > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
