Comments (9)
I'm using doxygen-awesome-css (example) for one of my libs and I quite like it. Not sure if it suits your purpose, but it's worth a look!
Works fine with Doxygen 1.9.6.
from cmake-init.
Yes, the situation around docs isn't the prettiest right now. Also mentioned in #41 (comment) I would be happy with an alternative solution.
from cmake-init.
Might be a dumb question to ask, but why do you use m.css
in the first place? If it's causing trouble and is on the edge of being abandonware why not use vanilla Doxygen instead? In the end, m.css
is just a skin that (significantly) improves Doxygen's visual appearance but it also brings in an unnecessary (?) sketchy dependency. I understand that the intention of this repository is to be opinionated but reverting to good old vanilla Doxygen would not rip out too much functionality and users are still free to throw in their own custom skins: https://doxygen.nl/manual/customize.html
My suggestion: separate the discussion about possible Doxygen replacements from the question whether m.css
is a good skin, e.g., by splitting the label doxygen
into two labels: doxygen
and m.css
.
from cmake-init.
The default Doxygen skin is really not good and as you answered your own question, it significantly improves the quality of the output. Having one less thing to setup in an initializer utility is a good thing.
As mentioned in #58, I would be happy to move to alternatives as well. If you think you can improve things in this area, PRs are also welcome. I have a bit less time nowadays to do a lot of extra research in this area.
from cmake-init.
Well, my suggestion is to get rid of m.css
but I fully appreciate different opinions about that; but I will not bother to make PRs if you had reasons to choose m.css
and would decline the PR anyhow. AFAIK, you are not losing any features (besides visual appearance) by abandoning m.css
. However, these doxygen
issues are not genuine Doxygen problems but m.css
issues and for the sake of transparency, you should rename this label.
from cmake-init.
m.css also provides a quick search that I really really like. It's a small thing, but it's gives that polished feel and makes looking for things much easier. Check the m.css demo: https://doc.magnum.graphics/magnum/
from cmake-init.
Fair enough:)
from cmake-init.
In fact, I'm going to mention it separately here that I really don't like how cppreference removed their own search feature and instead co-opted to use DDG. You used to get a small popup that showed you results as you typed. I think it's a real issue that now you get redirected to get search results. My insistence in this regard probably reflects this annoyance of mine.
from cmake-init.
Thinking about this issue a bit longer I think that the current solution is actually fine. From a user perspective, it is easier to remove m.css
and to fall back to vanilla Doxygen than to include it post hoc.
from cmake-init.
Related Issues (20)
- cmake does not detect some vcpkg installed libraries when using cmake-init HOT 8
- Web cmake-init HOT 2
- Not Compatible with Conan 1.51.x HOT 2
- Build failure on the dev branch
- How to link additional libraries HOT 1
- Thin mode
- `sanitize` job fails in new project HOT 3
- `fmt/core.h` not found HOT 6
- Spell and grammar checking
- Add sanitizer option to user presets HOT 5
- Why is the template generate a CMakeUserPresets, should not those be outside of git and local to the dev own setup?
- Showcase insertion of CMake variables via `configure_file()` HOT 3
- Conan v2 template HOT 3
- Mingw support in cmake-init HOT 1
- MSVC's /analyze is erroneous and slow
- It seems that my previous installation of Visual Studio 2022 edited my configurations HOT 2
- Rethink flags presets HOT 3
- Errors with `-fcf-protection=full` on darwin (CMakePresets.json, "flags-darwin" preset) HOT 2
- Runtime error (Error code: 0xc0000135) when building shared libraries on Windows using MSVC HOT 3
- Setting `-D<project>_INSTALL_CMAKEDIR=something` produces unexpected results HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cmake-init.