Hi Gianluca, <div>I can't say how much I could dedicate to that, but if you could put it on GitHub I could find some time to contribute.</div><div>I don't think I can invest time on the low level development, but with Python I think I could give some time.</div>
<div><br></div><div>giovanni<br><br><div class="gmail_quote">2011/3/31 gianluca.massei <span dir="ltr"><<a href="mailto:g_massa@libero.it">g_massa@libero.it</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
hi camilo, I'm working to make a qgis-saga interface me too, but with a "python approach". I haven't published my code because it's very experimental and really not usable. Anyway, at moment I can access from QGIS to saga via a simple menu. After the call, each module print to stdout the "help" output (like "saga_cmd library_name module name -h"). I'm working to build GUI "on the flay" with pyQT but progress is really slow.<br>
If you think to use python I'm happy to work togheter and I'll put my rough code on GitHub. Otherwise, don't know C++ enough to really contribute at the develop of plugin.<br>
<br>
Hi<br>
<br>
Gianluca<br>
<br>
<br>
Il 30/03/2011 13.16, Camilo Polymeris ha scritto:<div><div></div><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello, Paolo, and thanks for your swift answer.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Please do: I think this is quite interesting. Please note that Gianluca<br>
Massei has started some work on this, so he may be able to start<br>
quicker.<br>
</blockquote>
Has Gianluca published his code? I'd like to see his approach and<br>
maybe work together. Mine is at github, BTW, but is completely<br>
unusable right now. Just experiments.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think a C++ plugin has limited chances to be successful, because it<br>
would either require a dependency of QGIS on SAGA, or the recompilation<br>
of the plugin for each distro. Previous experiences in this direction<br>
resulted in wonderful plugins used by very few people.<br>
Python is the way to go IMHO.<br>
</blockquote>
I may be wrong, but wouldn't a recompilation of the saga modules and<br>
saga API be necessary either way? Unless you install the full SAGA<br>
package. Even then, I am not sure if saga packages for all distros<br>
include the python bindings. These would have to be generated (SWIG)<br>
and compiled, too.<br>
Anyway, I was thinking more of a low level approach, dynamically<br>
loading the libraries and taking care of data structure exchange,<br>
which means this plugin wouldn't have the same requirements as most.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think you should be able to complete the interface at least. Adding<br>
all the modules may be postponed, if it proves too long. See the<br>
GdalTools approach for this. Also the GRASS plugin should give you<br>
insights.<br>
</blockquote>
I'll try to identify the most used data structures and formats, see if<br>
there are some I can skip for now. Also I may leave out interactive<br>
modules, if necessary. Just to simplify things in the beginning.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
GUI: Any ideas? So far I think I'll just clone SAGA's.<br>
</blockquote>
I think it would be good if you could follow either the GdalTools or the<br>
GRASS plugins approach.<br>
</blockquote>
I will take a look at that, considering that I have to generate the<br>
interface on-the-fly based on module parameters and input data. I find<br>
specially SAGA's handling of interactive modules a little confusing:<br>
often it is not clear to the user (me, at least) what he is expected<br>
to do next.<br>
<br>
One of the difficulties I have faced is generated by SAGA's<br>
documentation. I thought I knew the API more or less well, but this<br>
new project as forced me to use parts I hadn't looked at before.<br>
<br>
Well, thanks again for your comments.<br>
<br>
Regards,<br>
Camilo<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">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>
<br>
</blockquote>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">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>
</div></div></blockquote></div><br></div>