Hi all<br><br>+1 for using QProcess. I am using it in Lizmap Plugin to run external librairies (winSCP on windows, lftp on linux), and it works great. You can easily connect signals like readyReadStandardOutput(), readyReadStandardError() and finished(int, QProcess::ExitStatus) to your plugin methods. <br>
<br>Michael<br><br><div class="gmail_quote">2012/5/13 Etienne Tourigny <span dir="ltr"><<a href="mailto:etourigny.dev@gmail.com" target="_blank">etourigny.dev@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Victor,<br>
<br>
I agree on all your points.<br>
<br>
May I suggest to have a unique interface/approach that other existing<br>
interfaces can benefit from (i.e. standalone gdaltools and ftools).<br>
<br>
It seems that QProcess is an interesting candidate (and QThread when<br>
not using external app.), because it works in both c++ and in pyqt<br>
(ref. gdaltools) - plus there is already code inside qgis that uses<br>
it.<br>
<br>
my 2 centavos<br>
<span class="HOEnZb"><font color="#888888">Etienne<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Sun, May 13, 2012 at 6:13 PM, Victor Olaya <<a href="mailto:volayaf@gmail.com">volayaf@gmail.com</a>> wrote:<br>
> Here is my opinion on all that, in short:<br>
><br>
> -The main idea of using threads is not now to execute multiplep<br>
> algorithms at the same time, so we can remove a lot of complexity<br>
> (like 2 processes writing the same file, as it was mentioned)<br>
><br>
> -Implementing a canceling mechanism is going to be the greatest<br>
> improvement once we have the threading stuff<br>
><br>
> -So, for me, this is what should be done:<br>
><br>
> 1)implementing the threading part<br>
> 2) implement the cancelling mechanism (a responsive cancel button, etc)<br>
> 3) modifying algorithm to respond to cancellin events.<br>
><br>
> I think that would be more than enough for a first part, and it would<br>
> be a great improvement for SEXTANTE<br>
><br>
> Regards<br>
><br>
> p.s. Just to let you know, I am leaving for Honduras tomorrow, and<br>
> will be there working for 2 weeks, so I not might be very active on<br>
> the lists during the next 15 days or so<br>
><br>
> 2012/5/13 Marco Hugentobler <<a href="mailto:marco.hugentobler@sourcepole.ch">marco.hugentobler@sourcepole.ch</a>>:<br>
>> Hi Alex<br>
>><br>
>><br>
>>>Also I think about rewritting fTools in C++ and integrating its<br>
>>>algorithms into QGIS<br>
>>>analysis library. This makes tools a bit faster and will allow to use<br>
>>>algorithms in<br>
>>>plugins<br>
>><br>
>> That would be a great enhancement and leverage the analysis library as a<br>
>> whole.<br>
>><br>
>> Regards,<br>
>> Marco<br>
>><br>
>><br>
>><br>
>><br>
>> On 13.05.2012 09:23, Alexander Bruy wrote:<br>
>>><br>
>>> Hi Etienne,<br>
>>><br>
>>> 2012/5/12 Etienne Tourigny<<a href="mailto:etourigny.dev@gmail.com">etourigny.dev@gmail.com</a>>:<br>
>>>><br>
>>>> I stand corrected then - I guess I was confusing it with ftools, which<br>
>>>> is blocking and does not spawn a process.<br>
>>>> Any way ftools could be adapted to use the same approach as gdaltools?<br>
>>><br>
>>> most fTools functions already implemented as threaded, but there are some<br>
>>> minor issues. I work on improving processes handing in fTools, and several<br>
>>> tools already don't block main QGIS window, has non-modal dialogs and<br>
>>> allows<br>
>>> to cancel running process.<br>
>>><br>
>>> Also I think about rewritting fTools in C++ and integrating its<br>
>>> algorithms into QGIS<br>
>>> analysis library. This makes tools a bit faster and will allow to use<br>
>>> algorithms in<br>
>>> plugins<br>
>>><br>
>><br>
>><br>
>> --<br>
>> Dr. Marco Hugentobler<br>
>> Sourcepole - Linux& Open Source Solutions<br>
>> Churerstrasse 22, CH-8808 Pfäffikon SZ, Switzerland<br>
>> <a href="mailto:marco.hugentobler@sourcepole.ch">marco.hugentobler@sourcepole.ch</a> <a href="http://www.sourcepole.ch" target="_blank">http://www.sourcepole.ch</a><br>
>> Technical Advisor QGIS Project Steering Committee<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Qgis-developer mailing list<br>
>> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div><br>