On Sat, Jul 2, 2011 at 2:37 PM, Camilo Polymeris <span dir="ltr"><<a href="mailto:cpolymeris@gmail.com">cpolymeris@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I have now invested a week trying to reconcile traits & the processing<br>
framework, without satisfying results. It may have to do with me not<br>
having any experience with traits.. but I must admit, I am quite<br>
confused and not sure how to proceed.<br>
<br>
Would appreciate if someone else can have a look at the code (traits<br>
branch) and comment.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
Regards,<br>
<br>
Camilo<br></div></div></blockquote><div><br></div><div>I don't know if this is relevant to the crashes you have been getting, but TraitsUI and most other Enthought Qt-oriented GUI projects use version 2 of the SIP QString and QVariant APIs:</div>
<div><br></div><div> <a href="https://github.com/enthought/pyface/blob/master/pyface/qt/__init__.py">https://github.com/enthought/pyface/blob/master/pyface/qt/__init__.py</a></div><div><br></div><div>This is done so they can swap between PyQt4 and PySide without hassle and to get better unicode and Python 3 support. QGIS uses Version 1 of those APIs which is fundamentally incompatible. QGIS could upgrade to version 2 but all Python plugins containing code using QString or QVariant would have to replace these calls with plain Python strings and objects---definitely a "2.0" sort of change.</div>
<div><br></div><div>-Charlie</div></div>