nsf

   - Switch to print_name() for rendering entity names for the search       box     - Fixed the @parameter generation in method.html.tmpl     - @glossary: Support for referencing glossary entries with certain       formatting annotations: @gls (minor letters only), @Gls (title),       @glspl (plural), @Glspl (title plural), ...  Added explicit       acronym rendering (long and short forms): @acrfirst, @acr;       fixing an id-generation issue for @glossary entities     - Completed the first round of amending nx.nxd with @glossary entries       and references.     - I got rid of curly braces ("{", "}") as marker symbols ("{{...}}",       "{{{ ... }}}") for formatting fragments of comment blocks. They       proofed sufficiently hairy due to their heavily loaded meaning for       the Tcl parser (the unclosed brace issue in Tcl comment blocks, the       list-like processing in our comment block parser, ...). Instead, I       introduced <<...>> for link-like elements (anchors, glossary       references) and MediaWiki-like '''...''' blockmarkers for code       listings. Thanks to Victor Guerra for reviewing and discussing this       concrete-syntactic design decision.     - Increased the robustness of line-by-line parsing for comment       blocks. Within the comment block parser, we operate on comment lines       as Tcl lists (lindex, lassign, ...). While convenient from a       processing perspective, this risks limiting the degrees of freedom       when writing comments (e.g., using tabs and spaces to indent inline,       grouping words to form lists of lists, ...). By leveraging "args"       argument processing through [apply] for line preprocessing, we balance       the two requirements.     - Verified that @use works between objects and methods.     - Some cleanup in the mixin layer code     - Resolve interp-alias chains to entity class objects explicitly     - Adjusting the Container/Containable mechanism to apply only to part       classes relevant to particular container entities.     - Fixing support for package rendering as top-level entities (e.g., in       the leftbar menu)     - Providing the project object to all entities subject to template       processing.     - Declaring some forwarders public explicitly (to reflect recent       changes in the reach of default call protection)

Show less