[scribus-dev] Scripter: Your feedback is required
avox at arcor.de
Fri Apr 11 09:37:39 UTC 2014
Currently we use PyQt, which in turn uses SIP. That way we only have to register the right QObjects and PyQt does the rest.
If I understand correctly, PySide does something similar?
From: Chris Barker [mailto:chris.barker at noaa.gov]
Sent: Donnerstag, 10. April 2014 19:12
To: Scribus Development Mailing List
Subject: Re: [scribus-dev] Scripter: Your feedback is required
On Thu, Apr 10, 2014 at 9:22 AM, Mark Heieis <mheieis at alois.ca> wrote:
I'd be delighted to see "scripter2" see daylight. Especially if the scribus CLI option was also available (not sure if this happened or was just a thought).
I've being toying with porting "scripter2" as a personal project using qt5, python3 and c++11 for a bit with some limited success.
My questions are:
1) What is it's current status?
2) Has there been any work done on it?
Sorry for being too lazy to go find the code, but a question:
What tool(s) are being used to develop the Python / C++ bridge? This can make all the difference as to how easy it is to write a robust Python API.
If you want to be able to script the GUI, then it may make sense to use PySide, and then use it's tool for developing other C++ / Python bindings:
Otherwise, I'm a big fan of Cython for calling C/C++ code from Python. It allows tight integration and complete control and best-possible performance. And there is X-Dress, for auto-generating Cython code that calls C/C++. I haven't actually tried that yet, though...
Christopher Barker, Ph.D.
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the scribus-dev