summaryrefslogtreecommitdiffstats
path: root/imports
Commit message (Collapse)AuthorAgeFilesLines
* Convert to cmakeShawn Rutledge2023-06-014-20/+83
| | | | | | | | | | | | | | | | | | | | 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>
* UmlSequenceDiagram: use Flickable.AutoFlickIfNeededShawn Rutledge2016-06-161-0/+1
| | | | | | | No need to scroll horizontally if the diagram fits. Change-Id: I9b5cbd4c13af42b9db2e7e50e9ca4f40b5971730 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* install QML for viewing Sequence diagrams; remove uq scriptShawn Rutledge2016-06-1010-0/+14
| | | | | | | | | | | | 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>
* QmlMessageTrace: detect and combine repeated sections of backtracesShawn Rutledge2016-06-101-4/+5
| | | | | | | | | | | | If there are multiple tracepoints, it happens quite often that the most recent backtrace contains the backtrace that we already captured in handling the previous tracepoint. If the time difference is small enough and we find such a duplicated sequence of methods, don't repeat the Message output in the trace QML: pick up where the previous trace left off. Change-Id: I32f47430ab44fd7570569e0f347784d23197a3bc Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* add QmlMessageTraceShawn Rutledge2016-06-102-5/+11
| | | | | | | | | A utility to be instantiated in the application-under-test, which will install itself as the message handler, parse the output of the requested logging categories for tracing, and generate a message trace in QML. Change-Id: I3961c27d00ecead5a1204cb2f6928af4f9da26aa Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* use QtQuick.Controls 2; use qml runtime; tooltip for detailsShawn Rutledge2016-06-073-83/+76
| | | | | | | Also a Quit shortcut, and better zooming behavior, and some simplification. Change-Id: I6a14639c0c555692e862298815c719008a4e9668 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* swap license: even the QML is LPGL3 / GPL3 nowShawn Rutledge2016-06-065-154/+139
| | | | | | | | | We used to think that qml ought to always be BSD. But now following the example of the QtQuick Controls 2 project. The date and Digia -> Qt Company needed to be updated anyway. Change-Id: I487fe4b1ce093abef2902ff7bcf087a43ff7f5fd Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
* initial working version with examplesShawn Rutledge2013-09-198-0/+452
try ./uq examples/flickable.qml Change-Id: Id684edaf55155fcd32fc535f16f3145d945a2697 Reviewed-by: Shawn Rutledge <shawn.rutledge@digia.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-26 09:42:13 +0000