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

Use doxygen to document QLever? #618

Closed
dpriskorn opened this issue Feb 26, 2022 · 5 comments
Closed

Use doxygen to document QLever? #618

dpriskorn opened this issue Feb 26, 2022 · 5 comments

Comments

@dpriskorn
Copy link

https://www.doxygen.nl/index.html

@joka921
Copy link
Member

joka921 commented Feb 27, 2022

We are already working on commenting any new and updated code in the Doxygen format. At some point it would probably be nice to actually generate the docu, especially if people are interested in contributing to the QLever codebase (See also my Email from today).

@hannahbast
Copy link
Member

hannahbast commented Feb 27, 2022

It's trivial for anyone to generate that documentation theirselves: just checkout the code and run doxygen.

I am not sure how useful that is though. The code is already on GitHub, where you can look at it with nice syntax highlighting. Doxygen offers little added value on top of that.

What would be of very significant added value is a document that describes the overall design of QLever, with a good overview over which components there are, the principle ideas behind them, and how and where they are implemented in the code. As I said, I will start writing that document soon.

@dpriskorn
Copy link
Author

Class hierarchy is one thing it can generate. That way you can get a high level overview of the classes.

@hannahbast
Copy link
Member

hannahbast commented Feb 27, 2022

@dpriskorn Not really useful in my experience without an accompanying document explaining it. Especially not for a very large project with very many classes

@hannahbast
Copy link
Member

Interesting discussion, but not an open issue anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants