On Monday, August 15, 2011 10:15:35 Aaron J. Seigo wrote:
> > On Mon, Aug 15, 2011 at 5:34 AM, Aaron J. Seigo wrote:
> > > complex types from Python will not be able to be used from users of
> > > the>
>
> DataEngine. the data is being exported from the Python runtime, after
>
> > > all. you'll
On Mon, Aug 15, 2011 at 10:30 AM, Luca Beltrame wrote:
> In data lunedì 15 agosto 2011 09:37:29, Eric Mesa ha scritto:
>
> > its XML structure, right? So the QML can just treat it as XML later?
> IOW,
> > I don't want to lose the benefit of XML's structured data.
>
> If you turn it into a QVaria
In data lunedì 15 agosto 2011 09:37:29, Eric Mesa ha scritto:
> its XML structure, right? So the QML can just treat it as XML later? IOW,
> I don't want to lose the benefit of XML's structured data.
If you turn it into a QVariant, there's an additional PyQt method to turn it
back into a Python
On Monday, August 15, 2011 09:37:29 Eric Mesa wrote:
> On Mon, Aug 15, 2011 at 5:34 AM, Aaron J. Seigo wrote:
> > complex types from Python will not be able to be used from users of the>
DataEngine. the data is being exported from the Python runtime, after
> > all. you'll need to simplify the ret
On Mon, Aug 15, 2011 at 5:34 AM, Aaron J. Seigo wrote:
>
> complex types from Python will not be able to be used from users of the
> DataEngine. the data is being exported from the Python runtime, after all.
> you'll need to simplify the returns, e.g. turn the XML into a string and
> the
> provid
On Saturday, August 13, 2011 17:07:31 Eric Mesa wrote:
> Now, views.py, the program script it's calling is returning a tuple with the
> first entry being an XML object and the second being a list.
complex types from Python will not be able to be used from users of the
DataEngine. the data is bein
