Well, I don't mean to remove the possibility to interact with the GUI from the algorithms, rather I would abstract the interaction and route it to the GUI in case we are inside QGis GUI or to the console output if we are in a CLI...<div>
<br></div><div>giovanni<br><br><div class="gmail_quote">2012/5/8 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">
Good idea - and have gui classes that call the algorithms. I don't<br>
know how many files/classes you have, but it might be a pain to<br>
separate the gui from the execution code if you have many algorithms.<br>
<br>
Etienne<br>
<div><div class="h5"><br>
On Tue, May 8, 2012 at 8:58 AM, G. Allegri <<a href="mailto:giohappy@gmail.com">giohappy@gmail.com</a>> wrote:<br>
> Almost all the actual algorithms assume to be inside a QgisApplication. It's<br>
> obvious, being born as QGis plugins.<br>
> Anyway, I think it would be a good plus being able to run (most of) them<br>
> from a CLI, given that SEXTANTE handles the layers I/O from filesystem.<br>
> If I remove QtGui calls from my algorithms, they could be used from console,<br>
> as far as I have an out-of-gui version of AlgorithmExecuter and QgsLayers.<br>
><br>
> What do you think about this?<br>
> giovanni<br>
><br>
</div></div>> _______________________________________________<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>
</blockquote></div><br></div>