Algorithms Library Toolkit Core issueshttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/-/issues2021-11-21T12:06:33+01:00https://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/-/issues/219idea: Autogenerate documentation by Doxygen2021-11-21T12:06:33+01:00Tomáš Peckaidea: Autogenerate documentation by DoxygenI think we could generate the actual documentation from the actual docstrings in the c++ code.
* Just let Doxygen do its magic before anything else happen. This outputs an XML
* Now, in compile time we should parse the XML and the `regi...I think we could generate the actual documentation from the actual docstrings in the c++ code.
* Just let Doxygen do its magic before anything else happen. This outputs an XML
* Now, in compile time we should parse the XML and the `registration` code from any `alib2algo` `.cpp` file should take what it needs from there.
However, can this be done in compile time or do we need to bundle the doxygen output and do this on library load by the CLI?Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/-/issues/191cmake: add support for non-installed libraries, aql should link alib2dummy in...2020-04-11T15:12:31+02:00Tomáš Peckacmake: add support for non-installed libraries, aql should link alib2dummy in some situations- `alib2dummy` lib is installed, remove this behaviour
- aql should depend on alib2dummy but not in install mode- `alib2dummy` lib is installed, remove this behaviour
- aql should depend on alib2dummy but not in install modeTomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/-/issues/154Structure installed headers2019-07-17T10:07:11+02:00Tomáš PeckaStructure installed headersAll the headers are placed inside `.../includes/algorithms-library/` unorganized.
I think we should consider keeping the module structure, for example:
- `/includes/algorithms-library/arbology/exact/BoyerMooreHorspool.h`will become
- ...All the headers are placed inside `.../includes/algorithms-library/` unorganized.
I think we should consider keeping the module structure, for example:
- `/includes/algorithms-library/arbology/exact/BoyerMooreHorspool.h`will become
- `/includes/algorithms-library/algo/arbology/exact/BoyerMooreHorspool.h`
Reasons:
- While splitting packages into two (alt, alt-gui), I have a hard time finding what headers are from gui
- I dont really like mixing top-level directories `Graphics`, `arbology` or `ast`.v0.0.1