Present and future of Qt for Python: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
Line 13: Line 13:
Open Discussion:
Open Discussion:


* 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, Rapid Prototyping, even theming?
* Uses cases, Rapid Prototyping, even theming?
* Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think newVIM's Lua bindings)
* Creator: Text macro/todo, VCS plugin, LSP interaction of text editor (think newVIM's Lua bindings)

Revision as of 14:29, 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)
Retrieved from "https://wiki.qt.io/index.php?title=Present_and_future_of_Qt_for_Python&oldid=41008"