Dr. Markus Voss

Results 9 issues of Dr. Markus Voss

**Is your feature request related to a problem? Please describe.** use Hyperlinks on elements so that a architecture documentation comes out that can be clicked onto the elements and leads...

enhancement

**Is your feature request related to a problem? Please describe.** A hierarchical tree view of cheat sheet contents would be nice to see the parent/child dependencies.

enhancement

**Is your feature request related to a problem? Please describe.** to solve the bug that the footer cannot be configured to vanish in the project-specific config file (issue #31), the...

enhancement

**Is your feature request related to a problem? Please describe.** The current markdown files for - Readme - Examples - Modelling Guideline - User's Guide do not have a table...

documentation

**Is your feature request related to a problem? Please describe.** An editor plugin could give quick help on macro usage, generate unique aliases and do auto-completion for the macros. also...

enhancement

**Is your feature request related to a problem? Please describe.** if a file is marked with "'PUMLAMR", then it can be assumed that there would be at least one re-usable...

enhancement

**Is your feature request related to a problem? Please describe.** Similar as the "InjectChildElements". When modeling the standard example for the C4 model, the need for this arose, as I...

enhancement

**Is your feature request related to a problem? Please describe.** Currently pumla does not support the rendering of diagrams. You have to do it manually. **Describe the solution you'd like**...

enhancement

**Is your feature request related to a problem? Please describe.** Currently interfaces are just named bobbles. There is no "type" information behind (in a diagram you can of course model...

enhancement