QtCS25 - Developer tools feedback

Session Summary

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum.

Session Owners

Kai Koehne Tuukka Turunen

Notes

Tasks for developer tools

• Project setup & configuration
  • Github Integration (VS Code certainly has an edge there)
  • Tweaking local configuration anew
  • Integration with other platforms
  • Problematic: Qt Account (for use cases where the one installing is not the end user)
  • Command line wizards
• Understanding unfamiliar code
  • Improving integration with Axivion tools?
  • Qt Documentation quality good
  • Bug report: F1 context is not always correct (e.g. for common methods like size())
  • Ship with C++ std qch ??? Cf. https://bugreports.qt.io/browse/QTCREATORBUG-22334
• Code editing, refactoring, testing
  • Refactoring: A lot of space for improvements on C++ side
  • Refactoring: Optimize use case to change .ui.qml / .qml properties
  • also: refactor out items into separate components
• Debugging, profiling & optimizing
  • python3 in debugging helpers, x68 debugging on Windows
  • Frustrating factors: Windows, Android debugging
  • macOS: "Leaks" support (valgrind doesn't work on macOS/ARM)
  • QML Profiling: Lower-level information for profiler (if it is provided already?)
    • Profiler could be generalized to generic tracing (move QML profiler to Qt Core, replace TCF)?
    • Clarify terminology: "Compiling" is not actually compilation, and Qt QML Compiler won't help
• Building, deploying, running
• Localization
  • People don't find standalone Linguist
    • Online Qt Linguist in WebAssembly?
• Collaborating with the team
  • Code sharing?
  • Sharing settings/setup
• Packaging & publishing