Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Doxygen #106

Open
fuchsto opened this issue Nov 15, 2016 · 9 comments
Open

Update Doxygen #106

fuchsto opened this issue Nov 15, 2016 · 9 comments

Comments

@fuchsto
Copy link
Member

fuchsto commented Nov 15, 2016

Everyone (yes, you @dash-project/developers):

@fuchsto
Copy link
Member Author

fuchsto commented Nov 17, 2016

@devreal Great effort, thank you a lot!

@JosefSchaeffer
Copy link
Member

Created a branch sup-106-dash-doxygen for doxygen documentation.

@fuchsto
Copy link
Member Author

fuchsto commented Nov 23, 2016

@dash-project/developers

IMPORTANT
Currently there is a bug in codedocs which prevents updates of the generated HTML files in browser cache.

To review doxygen output on https://codedocs.xyz/dash-project/dash either

  • clear your browser cache (via browser settings, <CTRL>+<F5> does not suffice) or
  • use incognito mode (starts with empty cache) (<CTRL>+<SHIFT>+N in chromium`)

@fuchsto
Copy link
Member Author

fuchsto commented Nov 23, 2016

@dash-project/developers
Examples are now nicely included in Doxygen.
For reference:

Please help documenting all examples in dash/examples, just use the \example tag as in dash/examples/ex.02.array/main.cpp.

@fmoessbauer
Copy link
Member

@dash-project/developers

Until now, there is not a single commit in sup-106-dash-doxygen. As discussed in the meeting, the documentation will be written in branch doc-106-dash-doxygen to bypass CI.

Please help us to complete the API documentation. Seriously!

@BenjaProg BenjaProg self-assigned this Dec 14, 2016
@fuchsto
Copy link
Member Author

fuchsto commented Dec 14, 2016

We use the following style for documentation:

/**
 * Multi-line comment opened with double-star /**.
 * First paragraph is brief description,
 *
 * Paragraphs are separated by empty comment lines. This is
 * the second paragraph and is not included in the brief
 * description.
 */
void wombatify(
   /// Single-line comments opened with *three* forward-slashes.
   /// This is a convenient way to describe function parameters.
   int     num_wombats,
   double  wombat_factor  ///< Postfix-style with <, comment placed *after* described parameter
) {
  // Any comment here is ignored, no matter how it is formatted.
}

@ddiefenthaler
Copy link
Contributor

Thanks for the introduction.

Is /// parameter documentation in any way preferred over \param or @param?

@fuchsto
Copy link
Member Author

fuchsto commented Dec 14, 2016

@ddiefenthaler Don't use the Java-style @param, please. Apart from that, use whatever you prefer.
I personally like the inline style /// Param description because undocumented parameters are easier to spot.

@fuchsto
Copy link
Member Author

fuchsto commented Dec 21, 2016

@dash-project/developers

I added a comprehensive style guide for Doxygen documentation in the contributor guide lines:

https://github.com/dash-project/dash/blob/development/CONTRIBUTING.md

Now, don't be shy and give it a try!

@devreal devreal modified the milestones: dash-0.3.0, dash-0.4.0 Sep 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment