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...
giovanni 2012/5/8 Etienne Tourigny <etourigny....@gmail.com> > Good idea - and have gui classes that call the algorithms. I don't > know how many files/classes you have, but it might be a pain to > separate the gui from the execution code if you have many algorithms. > > Etienne > > On Tue, May 8, 2012 at 8:58 AM, G. Allegri <gioha...@gmail.com> wrote: > > Almost all the actual algorithms assume to be inside a QgisApplication. > It's > > obvious, being born as QGis plugins. > > Anyway, I think it would be a good plus being able to run (most of) them > > from a CLI, given that SEXTANTE handles the layers I/O from filesystem. > > If I remove QtGui calls from my algorithms, they could be used from > console, > > as far as I have an out-of-gui version of AlgorithmExecuter and > QgsLayers. > > > > What do you think about this? > > giovanni > > > > _______________________________________________ > > Qgis-developer mailing list > > Qgis-developer@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/qgis-developer > > >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
