-
Notifications
You must be signed in to change notification settings - Fork 284
Future Work
Volker Krause edited this page Jun 28, 2017
·
25 revisions
Planned features that are not allocated to a release yet.
(Features that have been implemented can be looked up in the Road Map.)
- Mac bundle injector
- Injector auto-detector in the launcher to find the best available one
- Show filesystem watchers?
- Show running threads
- "static GammaRay", ie allow access to tools that merely introspect your Qt installation rather than a specific target from a stand-alone tool (fonts, locales, etc).
- generalized remote file system browser replacing the QRC browser, to e.g. also cover Android asset: VFS
- Add generic infrastructure for reporting detected problems in a central place, such as:
- shortcut conflicts
- modeltest issues
- nested layout margins
- dangling QStates
- C++ object origin tracing.
- global event filter, user selectable event type, dump all data contained in the corresponding event, and where it's addressed to
- same as above, but for native events
- trace propagation chain through items/widgets
- show running event loops and their backlog
- trace event sources to enable backtraces on deferred deletion or cross-thread invocations
- Runtime attachable model test
- Integration of Steve's proxy model tests and model test recorder
- Support style hints, layout spacing, sub-element rects
- Add QPaintBuffer paint introspection as done for QWidgets
- Allow to modify QStyleOption parameters
- Provide dummy widgets for styles that crash if the widget pointer is 0
- Model shows object rather than layout hierarchy
- a WebInspector/Firebug like QSS debugger
- Show signal/slot connections, and possibly also how often they are used
- See QtQuick2 page
- Binding visualization.
- Chart of QNetworkRequests / replies like the browser developer tools
- See for example https://blogs.kde.org/2010/05/01/qnetworkaccessmanager-proxy-classes
- Display timing info etc.
- Hook to force ignoring ssl errors to allow use of MITM proxies such as Burp suite for debugging purposes
- Display the SSL backend in use and version details
- Cookie jar editor.
- Access to QSslConfiguration
- QSettings browser
- scene graph view with remote view and entity picking support.
- frame graph view with access to intermediate rendering results and assembled render view commands
- material inspector
- display input aspect configuration
- access to backend structures
- manual override of the GPS position, with support for track replay
- can we capture the paint commands on a QPrinter for display in the paint analyzer somehow?