alialib / alia Goto Github PK

We should use a more accurate non-linear blending technique or perhaps even switch to a different color space and/or library.

The current usage is inconsistent with how CSS uses it.

There's too much duplication going on between the docs and the code, and, especially if the docs are going to stay in their own repository, there needs to be a way to pull the documentation for individual functions from the code into the official docs.

The obvious choice is Doxygen, but integrating it with Docsify is not trivial. Switching to Sphinx/Breathe is an option, but also a lot of work. There may be options to embed fragments generated by Sphinx/Breathe into the Docsify docs. It may be worthwhile to look at doing custom processing of the Doxygen XML files and directly render them as HTML. This has the side benefit that we could do custom corrections to account for the fact that Doxygen doesn't deal well with modern C++. It might even be a good exercise to do this processing in alia/HTML.

Maybe Standardese is also worth considering?

named_blocks might be leaked if they disappear during a partial refresh. Add a test case for this.

Include processing of callbacks, any updates to the DOM, etc. Using spdlog seems to make sense.

The types should be aware of the 'inheritance' relationships and only allow conversions where appropriate.

After including in the header why does it not recognize the html:: namespace?

• Show examples of removing items
• Get rid of the ctx argument

And add a disclaimer that it needs to be updated