Present and future of Qt for Python: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Created page with "Category:QtCS2023 ==Session Summary== ==Session Owners== ==Notes==")
 
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:QtCS2023]]
[[Category:QtCS2023]]
==Session Owners==
* Shyamnath Premnadh
* Adrian Herrmann


==Session Summary==
==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?


==Session Owners==
Open Discussion:
 


==Notes==
* 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)

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)