Present and future of Qt for Python: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:QtCS2023 ==Session Summary== ==Session Owners== ==Notes==") |
m (→Notes) |
||
Line 7: | Line 7: | ||
* QtScrypt use cases: Creator / Design Studio (internal), Blender | |||
* iOS? (C++ no one), Qt iOS still statically linked, Apple scripting restriction has been relaxed | |||
* Academy, what courses?: Python in QML?, bindings, Design Studio? | |||
Open Discussion: | |||
* Design Studio for PySide? | |||
* Design Studio Plugin API in Python: Quick3D scripting workflow like in Blender | |||
* Uses cases, Rapid Prototyping, even theming? | |||
* Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think newVIM's Lua bindings) |
Revision as of 14:28, 30 November 2023
Session Summary
Session Owners
- QtScrypt use cases: Creator / Design Studio (internal), Blender
- iOS? (C++ no one), Qt iOS still statically linked, Apple scripting restriction has been relaxed
- Academy, what courses?: Python in QML?, bindings, Design Studio?
Open Discussion:
* Design Studio for PySide? * Design Studio Plugin API in Python: Quick3D scripting workflow like in Blender * Uses cases, Rapid Prototyping, even theming? * Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think newVIM's Lua bindings)