Re: [Qgis-developer] SAGA Interface for QGIS - Final GSoC Report
> It's great to see the final touches improving the usability. > > Regarding the number of settings it would be good to offer as few > choices as possible. Many times the settings can be avoided and a > sensible default choice can be used. For example the setting "Number > of tags to show" is very confusing. Agreed, in general terms. What the right number of settings is, we'll find out through experimentation. As you probably noticed, the 'number of tags' slider doesn't actually do anything, yet. > For the module dialog the status bar could be changed to a simple > QLabel if you are not going to add further widgets or indicators to > it. The status bar also contains a superfluous size gripper for > changing dialog size. Additionally the Open and Save buttons simply > close the module dialog - that's a bit unexpected :) I use the size gripper! Sometimes the parameters don't fit horizontally, so I expand the dialog. Anyways, the feedback mechanism should be refined. I like those "non intrusive" pop-ups that e.g. firefox features, don't know if they are available in Qt, though. >> Finally, due to rising interest in interfacing other libraries (GRASS, >> OTB) I have published the API documentation[3] on the framework and >> started writing a Developer's Tutorial[4]. > > Thanks for the documentation. In the developer's tutorial I am missing > two important bits: > 1. how to implement the module's functionality when "Execute" button is > clicked Yes. The tutorial is in a very early stage. Next chapter will be about that. I am looking for some simple algorithm or library to have the demo module do something at least remotely realistic/useful. > 2. how to execute a module from a script or python console That would belong in the user's docs, I think. I have recently added some convenience functions. Will probably modify them, but for now you can e.g. type: from processing import framework framework["Pythagoras' Tree"].execute(Method = 2) See also issues #46 & #47 (github issue tracker). > It was great to have you aboard during the summer! We hope you enjoyed > it and you will continue hacking on the processing/SAGA tools to > support even broader range of modules and to make the user experience > as seamless as possible. And of course you are welcome to start > hacking on other parts of QGIS, too :-) Thanks! It has been a great opportunity and lots of fun. I certainly will continue hacking on the processing & SAGA code. In the long term, there are also some experiments I'd like to do with some geophysical models, to return a bit to the semantics of the problem. Regards, Camilo ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SAGA Interface for QGIS - Final GSoC Report
Hi Camilo On Sun, Aug 21, 2011 at 3:02 AM, Camilo Polymeris wrote: > Hello everyone, > > I am happy to say that this week saw many improvements in the QGIS > Processing Framework and the interface to SAGA. > > [...] It's great to see the final touches improving the usability. Regarding the number of settings it would be good to offer as few choices as possible. Many times the settings can be avoided and a sensible default choice can be used. For example the setting "Number of tags to show" is very confusing. For the module dialog the status bar could be changed to a simple QLabel if you are not going to add further widgets or indicators to it. The status bar also contains a superfluous size gripper for changing dialog size. Additionally the Open and Save buttons simply close the module dialog - that's a bit unexpected :) > Finally, due to rising interest in interfacing other libraries (GRASS, > OTB) I have published the API documentation[3] on the framework and > started writing a Developer's Tutorial[4]. Thanks for the documentation. In the developer's tutorial I am missing two important bits: 1. how to implement the module's functionality when "Execute" button is clicked 2. how to execute a module from a script or python console > Google Summer of Code 2011 is almost over, but it is my intention to > continue maintaining this software, first focusing on polishing the > available code and later adding more features: Support for further > parameter types, interactive modules, and module instance > serialization, among many other proposed. It was great to have you aboard during the summer! We hope you enjoyed it and you will continue hacking on the processing/SAGA tools to support even broader range of modules and to make the user experience as seamless as possible. And of course you are welcome to start hacking on other parts of QGIS, too :-) Regards Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SAGA Interface for QGIS - Final GSoC Report
Il 21/08/2011 03:02, Camilo Polymeris ha scritto: > implementation. The programmatically collected stats, indicating > support for 170 modules (40%) are published in the Module Support[1] > wiki page, while the Tested Modules[2] page, maintained by Paolo, > contains a list of SAGA modules that have actually been tested. Please note: due to time constraints, I'm able to properly test only a small subset of commands. Your help in testing more of them will be much appreciated. All the best. -- Paolo Cavallini: http://www.faunalia.it/pc ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] SAGA Interface for QGIS - Final GSoC Report
Hello everyone, I am happy to say that this week saw many improvements in the QGIS Processing Framework and the interface to SAGA. Primarily, raster input and output works now, thanks to help from SAGA developer Volker Wichmann. Single band local QGIS rasters are transparently converted to SAGA format using GDAL, processed, and imported back into QGIS. Many things could be improved and features added, but the basic functionality is there. To assess the progress of the interface, I have written a small script, which checks module support, as determined by parameter implementation. The programmatically collected stats, indicating support for 170 modules (40%) are published in the Module Support[1] wiki page, while the Tested Modules[2] page, maintained by Paolo, contains a list of SAGA modules that have actually been tested. Work on a settings dialog has started. It is still unclear how many and which settings should be left to the user. Also on the GUI side, an about dialog was implemented, which displays the new processing icon by Robert Szczepanek. In an effort to be consistent with the QGIS terminology, the string "raster" is now automatically substituted for instances of "grid" in each SAGA module's text: Names, tags, parameters and descriptions. Less visible to the user, but still important, the SAGA code has been refactored a little. Work is still pending on this issue. Additionally, the plugin's objects are now managed in a cleaner way. Validator and default value bugs have been fixed. Further testing is necessary. Finally, due to rising interest in interfacing other libraries (GRASS, OTB) I have published the API documentation[3] on the framework and started writing a Developer's Tutorial[4]. Google Summer of Code 2011 is almost over, but it is my intention to continue maintaining this software, first focusing on polishing the available code and later adding more features: Support for further parameter types, interactive modules, and module instance serialization, among many other proposed. Best regards & thanks a lot for the help, Camilo [1] https://github.com/polymeris/qgis/wiki/Module-Support [2] https://github.com/polymeris/qgis/wiki/Tested-Modules [3] http://polymeris.github.com/qgis/processing.html [4] https://github.com/polymeris/qgis/wiki/Developer%27s-Tutorial ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
