Present and future of Qt for Python: Difference between revisions
Jump to navigation
Jump to search
m (→Session Owners) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
[[Category:QtCS2023]] | [[Category:QtCS2023]] | ||
==Session | ==Session Owners== | ||
* Shyamnath Premnadh | |||
* Adrian Herrmann | |||
==Session Summary== | |||
* QtScrypt use cases: Creator / Design Studio (internal), Blender | * QtScrypt use cases: Creator / Design Studio (internal), Blender | ||
| Line 16: | Line 18: | ||
* 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, Rapid Prototyping, even theming? | * Uses cases, Rapid Prototyping, even theming? | ||
* Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think | * Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think Neovim's Lua bindings) | ||
Revision as of 15:46, 30 November 2023
Session Owners
- Shyamnath Premnadh
- Adrian Herrmann
Session Summary
- 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 Neovim's Lua bindings)