2010/2/17 Angel Pais <[email protected]>: > Hello Pete > > I'm convinced the best way to generate documentation is to develop a tool in > harbour itself. > I'm thinking on a DBF or sqlite3 based system with tags for titles, > description, sample code, related commands and functions, grouping options > etc. > That's the way Mr. Hannes Sieggler have made Alaska's and xharbour's > documentations. > From that you can generate anything you want, pdf, html ... > Using phyton to generate harbour documentation is very embarrassing. >
Hi! I don't want to start any flames. My intention is just help with a tool wich I have some experience. I disagree with your opinion. There's nothing embarassing using a tool (Sphinx) written in Python. Many things we use in day-to-day development are written in other languages, like editors, and even compilers. The Harbour compiler isn't written in Harbour. But it's just *my* opinion. I just want to help in documenting Harbour, whatever we will use for that, be it LyX, or something else. Regards! -- Daniel Gonçalves Base4 Sistemas Ltda. [www.base4.com.br] [twitter.com/spanazzi] _______________________________________________ Harbour-users mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour-users
