On 22/05/14 03:55 PM, Monique Semp wrote: > Hello, doxygen-users, > I’m using Doxygen to generate HTML output for a C++ library. Not all > the doc reviewers have direct access to the code that I’m commenting, > so I’ll need to solicit reviews by using the HTML output instead of > just having the engineers look at my code check-ins (for the doxygen > tags that I’m adding). > So do you have any recommendations for workflow and for how reviewers > can provide input in an easier fashion than saying, “on the > blah-blah-blah.html page, third para in the \this-tag, the “old-text” > should be “new-text”? > In theory I know that I can use Latex to create a PDF, which would > offer lots of commenting ability. But then the look-and-feel and > navigation is so different from what’s desired/delivered to the > customer that I doubt the value of such a time-consuming step. > Thanks for your thoughts, > -Monique Monique, Presuming there is no need to prevent access to the code because of security/propriety, can you expose the code via web page access? The reviews may not be able to "edit" the code directly but may be able to submit changes via diff.
There are some methods available depending on how the library is stored or accessed. For example, if source code was in an subversion repository, you could use an Apache module for people to access the library via a web page. This depends on how things are setup on your end. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
