Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

Qt Contributors Summit 2022 - Program/QtScrypt: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
 
Line 17: Line 17:
* Idea: Simplify CPython API/Create a high level API for it
* Idea: Simplify CPython API/Create a high level API for it
* QScryptEngine with an evaluate() function
* QScryptEngine with an evaluate() function
* QVariant-based (due to mixed types in Python
* QVariant-based (due to mixed types in Python)
* QScryptModule/QScryptFunction
* QScryptModule/QScryptFunction
* Some confusion about super ()
* Some confusion about super ()
Line 23: Line 23:
* Python scripting of Qt Design Studio was considered , but no capacity
* Python scripting of Qt Design Studio was considered , but no capacity
* Use Python instead of JavaScript in Qt Design Studio would be nice (developer POV) , for example Property Editor
* Use Python instead of JavaScript in Qt Design Studio would be nice (developer POV) , for example Property Editor
* Enable use of scientific packages from Python

Latest revision as of 12:30, 8 June 2022


Session Summary

Some time ago, I wrote a hackathon project to enable Python scripting within C++ applications - the outcome was cool :). Due to the similarities, I decided to call it QtScrypt, because it kind of follows a similar idea as QtScript, but with Python. I would like to present the proof of concept I have, and if it's interest from someone else to start the development and create a proper project out of this idea.

Session Owners

  • Cristián Maureira-Fredes

Notes

taken by Friedemann Kleint

  • Hackathon Project running Python from C++ (Qt Script)
  • Idea: Simplify CPython API/Create a high level API for it
  • QScryptEngine with an evaluate() function
  • QVariant-based (due to mixed types in Python)
  • QScryptModule/QScryptFunction
  • Some confusion about super ()
  • Application bindings exposing QObjects (as historically in Qt Creator)?
  • Python scripting of Qt Design Studio was considered , but no capacity
  • Use Python instead of JavaScript in Qt Design Studio would be nice (developer POV) , for example Property Editor
  • Enable use of scientific packages from Python