Hi Martin, <br><br><div class="gmail_quote">On Mon, Aug 15, 2011 at 12:48 AM, Martin Dobias <span dir="ltr"><<a href="mailto:wonder.sk@gmail.com">wonder.sk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
On Sun, Aug 14, 2011 at 5:58 PM, Giuseppe Sucameli <<a href="mailto:brush.tyler@gmail.com">brush.tyler@gmail.com</a>> wrote:<br>
> This week I've completed the import layer for the postgres provider.<br>
<br>
</div>Good to hear it is working. I will try to test that soon.<br></blockquote><div>thanks, I'm waiting your test result.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Please implement the support also for OGR provider - that should boil<br>
down to just a few lines of code when using QgsVectorFileWriter. In<br>
QGIS 2.0 we could move the code of this class to OGR provider and then<br>
remove that class. </blockquote><div>Of course, after SL provider the next one is OGR. I think I'll complete both <br>tasks in the next few days.<br>The GSoC coding period is going to end this week and I want complete <br>
that feature before the pencil down date.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">One more thing to consider for the importLayer<br>
functionality: providers may need some provider-specific options -<br>
e.g. in OGR this would be the name of the driver. That could be passed<br>
in another optional key-value parameter (QMap<QString,QString> ?)<br></blockquote><div>QgsVectorFileWriter also takes other parameters i.e. creationOptions and <br>layerOptions, both QStringList.<br><br>Probably a QMap<QString, QStringList> could be a better choise to handle <br>
with all them.<br>Do you agree with me?<br><br>Regards.<br></div></div><br>-- <br>Giuseppe Sucameli<br>