Hy Volker,
thanks for your code. I'm working for integrate it in SagaTools plugin.
As soon as the plugin is usable I will share it as sperimentale in qgis
repository.
by
gianluca
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
On Sat, Feb 19, 2011 at 1:09 AM, Volker Wichmann wichm...@laserdata.at wrote:
Hi Gianluca,
Another issue which has to be solved is that of the Grid System parameter.
As you most likely know, most of the SAGA grid modules require all grids to
be processed within the same grid system. In case
Il giorno sab, 19/02/2011 alle 01.09 +0100, Volker Wichmann ha scritto:
please find attached a first approach - the script takes a module
library name and a module name as input and parses all parameters. It
prints out the parameters sorted by input, output and options and also
prints out
On Thu, Feb 17, 2011 at 1:27 AM, Volker Wichmann wichm...@laserdata.atwrote:
Hi Gianluca,
My idea is to write a python code that will generate GUI
dialogs completely on the fly without any hard coded parameter flags or
.py files (SAGA has about 500 modules!). That is, you have a path where
It's a project we were thinking about a couple of years ago, but the project
has stopped (we've had to move the founds to other projects) The approach
was similar to yours, but I was thinking to a lower level binding: let saga
odules read directly from Qgis in memory data structures, without
Hi Volker,
In case your are interested in some python code which will parse the
above mentioned parameters, I can have a look within the next days.
Yes! I'm really interested! I'm not a really good python programmer and
any kind of help is wellcome.
Thanks
gianluca
Hi Johan, thank you for your interesting, suggestion and help:
* how are module libraries and modules presented? In a menu or some
type of module library?
I think to use a 2-level menu (libraries/modules)
* which qt interface would you like to use to present the different
type of parameters
Il giorno gio, 17/02/2011 alle 01.27 +0100, Volker Wichmann ha scritto:
the Gdal-Tools seem to be more or less hard-plugged: every tool has its
own description (.py file). Is your idea to generate these files (I'm
not familiar with pyQT, but I would expect that generating these files
would
Hi Volker, grazie per il tuo interessamento e il prezioso aiuto
I'm referring to files as accumulated.cost.spm attached this mail,
generated from Accumulated Cost Anisotropic module GUI. Although now
I've understand your opinion and I'm agree with you, my original idea
was to automaticaly
