Hi Martin, <br><br>GdalTools was based on the fTools structure. <br>So I think that every change we're doing on GdalTools should <br>be done on fTools too. Have we to inform Carson Farmer?<br><br><div class="gmail_quote">
On Tue, Jun 8, 2010 at 9:32 PM, Martin Dobias <span dir="ltr"><<a href="http://wonder.sk">wonder.sk</a>@<a href="http://gmail.com">gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Giuseppe<br>
<br>
2010/6/8 Giuseppe Sucameli <<a href="mailto:brush.tyler@gmail.com">brush.tyler@gmail.com</a>>:<br>
<div class="im">> Hi Martin,<br>
><br>
> now the modules import is done by the following lines:<br>
> from tools import GdalTools_utils as Utils<br>
> from tools import ( doBuildVRT, doContour, doRasterize, doPolygonize,<br>
> doMerge, doSieve, doProximity, doNearBlack )<br>
> from tools import ( doWarp, doGrid, doTranslate, doClipper, doInfo,<br>
> doProjection, doOverview, doRgbPct, doPctRgb )<br>
> from tools import ( doSettings, doAbout )<br>
><br>
> and GdalTools works fine until I reload it.<br>
> In fact, If I reload it I get this error:<br>
</div>> [...]<br>
<br>
This is an error caused by the unloader of plugins - I've found out<br>
that it fails to record the modules that are imported with syntax<br>
"from X import Y" and that results in some inconsistencies. I'm going<br>
to fix that soon.<br>
<br>
On a different note, I have a performance hint for GdalTools:<br>
It's not necessary to import all the do* modules at the startup. They<br>
are necessary only when they're triggered from the menu, so the import<br>
can be postponed to the point when they're needed and some time from<br>
the qgis startup can be saved. I see you load all the modules to check<br>
whether there aren't any missing dependencies. This could be actually<br>
done even easier:<br>
<br>
try:<br>
import osgeo.ogr<br>
import osgeo.gdal<br>
except ImportError:<br>
# tell user about missing python-gdal<br></blockquote><div> </div><div>Yes, we could load every do* module when required (on trigger) and <br>on startup try to import only the required modules.<br>I'm going to change it.<br>
<br>Cheers.<br><br></div></div>-- <br>Giuseppe Sucameli<br>