Thanks for the feedback I agree that it is better to keep things separate, but at the same time, the easier it is to have it all installed, the better for the final user.
I am planning to improve the checkings that are performed before an external algorithm is run, not just to check if the software is there or if a folder is configured (which can be a wrong folder), but to actually run a small algorithm, like a unit test. Maybe the first time that a SAGA or OTB algorithm is run, we can show the user a notice saying "Do you want SEXTANTE to check that the external application is correctly installed and configured?". and in case it is not, tell the user how to install it. I think this will avoid having users trying to run an algorithm that is not prepared to be run. From all the questions and reports I get about issues in SEXTANTE, some are caused by bugs in SEXTANTE or some data problem, but most are due to wrong setting of external apps or, in most cases, people not even knowing that you have to install them separately. I do not know how to easily solve this, but it clearly should be a priority... Thanks again 2013/2/23 skampus <[email protected]>: > Hi victor, i agree with you. > I do prefer to use sextante also for basic operations already present in > qgis menu. > It seems to me it is faster and i more appreciate temporary results > instead of the duty of creating definitive layers. > I don't know if it is correct, but could it be possible to include saga in > osgeo installer package? > > > > -- > View this message in context: > http://osgeo-org.1560.n6.nabble.com/Shipping-SAGA-with-QGIS-tp5036274p5036354.html > Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
