Present and future of Qt for Python: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 18: | Line 18: | ||
* Design Studio for PySide? | * Design Studio for PySide? | ||
* Design Studio Plugin API in Python: Quick3D scripting workflow like in Blender | * Design Studio Plugin API in Python: Quick3D scripting workflow like in Blender | ||
* Uses cases | * Uses cases: Rapid Prototyping, scripting, even theming? | ||
* Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think Neovim's Lua bindings) | * Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think Neovim's Lua bindings) | ||
Latest revision as of 15:53, 30 November 2023
Session Owners
- Shyamnath Premnadh
- Adrian Herrmann
Session Summary
- QtScrypt use cases: Creator / Design Studio (internal), Blender
- iOS: No C++ users present, Qt iOS still statically linked, Apple scripting restriction has been relaxed
- Academy: What courses? Python in QML?, bindings, Design Studio?
Open Discussion:
- No Qt for Python users present - what would make devs use it? Why interested?
- Design Studio for PySide?
- Design Studio Plugin API in Python: Quick3D scripting workflow like in Blender
- Uses cases: Rapid Prototyping, scripting, even theming?
- Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think Neovim's Lua bindings)