You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add tags to various methods and functions to show in which scenarios particular algorithms are useful. For instance, the tag transitions would be useful for both Fibonacci transitions and the procession algorithm.
Robodoc accepts the TAGS keyword, and will pull it into the HTML and other documentation format (e.g. https://michael-edwards.org/sc/robodoc/l-for-lookup_lsp.html#robo283), but it won't provide a link to those tags at the top right of the generated, HTML page, for instance, where functions, methods et cetera are linked. A single page with all of the tags listed, along with links to the code documentation for the particular functions and methods would be essential if this is to be at all useful.
The text was updated successfully, but these errors were encountered:
I investigated robodoc as well and had a brief look at the source where I wasn't able to locate any function for generating such a "tags-index". What about writing an issue to the robodoc repository (https://github.com/gumpu/ROBODoc)? It seems not to be completely inactive (at least the most recent commit dates to last year).
We should add tags to various methods and functions to show in which scenarios particular algorithms are useful. For instance, the tag transitions would be useful for both Fibonacci transitions and the procession algorithm.
Robodoc accepts the TAGS keyword, and will pull it into the HTML and other documentation format (e.g. https://michael-edwards.org/sc/robodoc/l-for-lookup_lsp.html#robo283), but it won't provide a link to those tags at the top right of the generated, HTML page, for instance, where functions, methods et cetera are linked. A single page with all of the tags listed, along with links to the code documentation for the particular functions and methods would be essential if this is to be at all useful.
The text was updated successfully, but these errors were encountered: