Hi DQMH Enthusiasts,
What we always do by adapting the std DQMH template is adding a logging functionality into the dequeue VI of the MHL of each module (our logger of choice is a LV wrapper around Log4Net, but it doesn't matter). In my recent project, I added this logging functionality also into every request and broadcast. That means I get a XML document that contains all messages that are sent and received. Then I wrote a parser that creates a plantuml sequence diagram out of the xml, because the sent messages had the same title as the received ones.
All I had to do to get a full blown sequence diagram of my application was to run a standard operation once and let the parser do its magic.
So my feature requests would be:
- add automated logging to each notification sent and received
- Create an add-on that takes a logging file and creates a Plantuml text from it
I am happy to help/demonstrate/explain what I did and what would be ideal. I know you guys think about logging, so this might be just a small step ahead.
Cheers, Niko
I'm declining this request because it's not directly related to the framework, but we implemented this request through LUMOS --> https://dqmh.org/product/lumos/