[Qgis-developer] Fwd: Threads in sextante

[Camilo Polymeris]

Hello all,
one of the things I will be implementing for sextante during GSoC will
be multithreading. I have experimented a bit with the possibilities
during the last few days, but it would be good to know your opinion on
what would be the simplest, cleanest solution.

At this point I feel the obvious place to introduce this functionality
is the AlgorithmExecutor class, as suggested by Victor, converting
that to an instantiable class, inheriting from QThread.
I tend to favor QThread over the python standard threads, because its
signaling system is familiar to all working with Qt and would interact
better with the existing GUI code.

In adition to the standard thread signals ("started", "finished",
"terminated"), the algorithm thread would emit "canceled", "error",
"feedback" and "percentageChanged" signals, when necessary. The later
two would be connected to Progress objects.

All GUI code would be moved out of AlgorithmExecutor.

Please comment if you see a better/easier way to implement this or any
potential pitfalls with this design,

Regards,
Camilo

---------- Forwarded message ----------
From: Paolo Cavallini <cavallini at faunalia.it>
Date: Thu, May 10, 2012 at 5:17 AM
Subject: Threads in sextante
To: Camilo Polymeris <cpolymeris at gmail.com>, Victor Olaya
<volayaf at gmail.com>, Alexander Bruy <alexander.bruy at gmail.com>,
Giuseppe Sucameli <sucameli at faunalia.it>


Hi all.
I'm here with Giuseppe AKA brushtyler, and we're having a very
interesting discussion
about threads & sextante. I would suggest to move the whole discussion to the ML
before starting to coda, as I see several alternative solutions to the
problem; some
of them may be unnecessarily complex, so perhaps all together we could design a
simple and effective solution.
Camilo, could you please resume the issue on the ML, so we'll start a
discussion there?
Thanks a lot.
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc