QtCS2017 Discuss Qt Logging enhancements: Difference between revisions
Jump to navigation
Jump to search
Arnaud Clere (talk | contribs) (added presentation summary) |
Arnaud Clere (talk | contribs) (discussion plan) |
||
| Line 3: | Line 3: | ||
* examining which enhancements would be useful to Qt | * examining which enhancements would be useful to Qt | ||
and how to contribute them... | and how to contribute them... | ||
==== Use Cases ==== | |||
help development | |||
help fixing bugs | |||
... | |||
==== Enhancements? ==== | |||
extended handler with format | |||
less literals in tracepoints | |||
TSV+JSON vs text-only | |||
Bind<TUserData> | |||
format-free handler | |||
performance requirements | |||
smart trace points (id, count, sampling) | |||
Revision as of 11:32, 9 October 2017
Qt-based devices such as Medical Cyber-Physical Systems could be developed, verified and validated more efficiently using structured logs. We suggest Qt Logging enhancements that would facilitate both human exploration and automated analysis with Python or other tools. The session will allow:
- gathering your feedback
- examining which enhancements would be useful to Qt
and how to contribute them...
Use Cases
help development
help fixing bugs
...
Enhancements?
extended handler with format
less literals in tracepoints
TSV+JSON vs text-only
Bind<TUserData>
format-free handler
performance requirements
smart trace points (id, count, sampling)