> Gerrit mentioned the documentation build times: those are a serious > problem. Doxygen takes longer than compiling the whole system (twice) > plus examples. For developing I turn off everything except the piece I'm > working on, and that's bearable, but not a good solution. I've tried > profiling doxygen a few times, and I couldn't come up with a quick fix > that significantly improved performance. Putting the .dox-equivalents > into the Wiki would be an option. I don't know if we need to get them > back at all. The only real loss would be the printed documentation, and > maybe offline browsing of documentation (not sure how much of a problem > that is these days). I could live with it, especially on Trac I think > it's easy to link from doxygen to Trac pages (I need to verify that).
micro-comments concering doxygen: (1) couldn't we use a script on the sourceforge servers which generates the doxyen html every night from cvs? or is this already done? (2) i completely agree that most of the param-names stand for themselves and that we don't need the "setX() sets variable X" type of docs. regards, simon ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
