summaryrefslogtreecommitdiffstats
path: root/umlquick.pro
Commit message (Collapse)AuthorAgeFilesLines
* Convert to cmakeShawn Rutledge2023-06-011-2/+0
| | | | | | | | | | | | | | | | | | | | There are two modules: one to generate traces at runtime, and one containing components used in the generated QML, needed to view the traces. We use add_subdirectory; there is some redundancy between the CMakeLists.txt in the subdirectories, but they are difficult to combine because of the use of per-module variables like module_dir, module_uri and module_version. We use PLUGIN_TARGET to get the backing code linked into the plugins (as was normal in Qt 5): Qt.labs.UmlQuick.Trace is a development-oriented module, generally used with temporarily-instrumented QML files, not meant for application deployment. Generated QML traces are generally viewed with the qml tool, so again it doesn't seem beneficial to have Qt.labs.UmlQuick.Sequence available in a separate backing library. Task-number: QTBUG-111946 Change-Id: Ia0f0b3bd43f64d0e0cfc67dd1e93165626a8c28b Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* install QML for viewing Sequence diagrams; remove uq scriptShawn Rutledge2016-06-101-0/+2
Now you can simply view the diagram QML with the qml runtime. The module is now renamed to Qt.labs.UmlQuick, with the Sequence (MessageTrace) diagram components being in Qt.labs.UmlQuick.Sequence and the trace instrumentation being in Qt.labs.UmlQuick.Trace. The diagram in UML terminology is called simply a Sequence diagram, whereas the act of generating one is to trace messages. Change-Id: I4d7db9eecc32af8b57c2c4242bb7d4568b777e28 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>