<div dir="ltr">On Fri, Apr 11, 2014 at 2:37 AM, Andreas Vox <span dir="ltr"><<a href="mailto:avox@arcor.de" target="_blank">avox@arcor.de</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="DE" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Chris!<u></u><u></u></span></p><p class="MsoNormal">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Currently we use PyQt, which in turn uses SIP. That way we only have to register the right QObjects and PyQt does the rest.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">If I understand correctly, PySide does something similar?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u></span></p></div></div></blockquote><div><br></div><div style>yup -- though I think it uses its own binding-generation tool, rather than SIP. Not sure why. IIUC, the primary point of PySide is to provide a LGPL, rather than GPL set of bindings. As Scribus is GPL (correct?) , then you might as well stick with PyQT and SIP.</div>
<div style><br></div><div style>So are you using SIP to wrap the non-QT parts of Scribus? I'd suspect that would be the way to go in this case, though I've never actually uses SIP....</div><div style><br></div><div style>
Sounds like you're in good shape to move this forward.</div><div style><br></div><div style>-Chris</div><div style><br></div><div style><br></div><div style><br></div><div style><br></div><div style><br></div><div style>
<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="DE" link="blue" vlink="purple">
<div><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">/Andreas<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Chris Barker [mailto:<a href="mailto:chris.barker@noaa.gov" target="_blank">chris.barker@noaa.gov</a>] <br>
<b>Sent:</b> Donnerstag, 10. April 2014 19:12<br><b>To:</b> Scribus Development Mailing List<br><b>Subject:</b> Re: [scribus-dev] Scripter: Your feedback is required<u></u><u></u></span></p></div></div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">On Thu, Apr 10, 2014 at 9:22 AM, Mark Heieis <<a href="mailto:mheieis@alois.ca" target="_blank">mheieis@alois.ca</a>> wrote:<u></u><u></u></p><div><div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><p class="MsoNormal">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).<br>
<br>I've being toying with porting "scripter2" as a personal project using qt5, python3 and c++11 for a bit with some limited success.<br><br>My questions are:<br><br>1) What is it's current status?<br>
<br>
2) Has there been any work done on it?<u></u><u></u></p></blockquote></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Sorry for being too lazy to go find the code, but a question:<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">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.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">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:<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal"><a href="http://qt-project.org/wiki/PySide_Binding_Generator" target="_blank">http://qt-project.org/wiki/PySide_Binding_Generator</a><u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">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...<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">-Chris<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">-- <br><br>Christopher Barker, Ph.D.<br>
Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R <a href="tel:%28206%29%20526-6959" value="+12065266959" target="_blank">(206) 526-6959</a> voice<br>7600 Sand Point Way NE <a href="tel:%28206%29%20526-6329" value="+12065266329" target="_blank">(206) 526-6329</a> fax<br>
Seattle, WA 98115 <a href="tel:%28206%29%20526-6317" value="+12065266317" target="_blank">(206) 526-6317</a> main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a> <u></u><u></u></p>
</div></div></div></div></div></div></div><br>_______________________________________________<br>
scribus-dev mailing list<br>
<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>
<a href="http://lists.scribus.net/mailman/listinfo/scribus-dev" target="_blank">http://lists.scribus.net/mailman/listinfo/scribus-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R (206) 526-6959 voice<br>7600 Sand Point Way NE (206) 526-6329 fax<br>
Seattle, WA 98115 (206) 526-6317 main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a>
</div></div>