Hi Radim and devs,<br><br><div class="gmail_quote">On Tue, May 24, 2011 at 4:44 PM, Radim Blazek <span dir="ltr"><<a href="mailto:radim.blazek@gmail.com" target="_blank">radim.blazek@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
QBrowser is just one use of QgsBrowserModel which was developed<br>
also as model for possible substitution of various "select layer" dialogs. </blockquote><div>I can use the QgsBrowserModel, no problem about this.<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">
Create/edit/drop tables and views is exactly what I would like to have<br>
also in QBrowser. But not only tables! ... Why queries<br>
could not be done in QBrowser or something similar?</blockquote><div>Allowing to run queries on database requires a lot of code in the provider and also <br>out of them, I should export methods to call the query, to get results, a class to <br>
map results, exceptions. Furthermore IMHO it's not good to implement this into <br>providers as they was thought to work with layers.<br><br>I couldn't use the QtSql module because its drivers are not in sync with <br>
database APIs used in providers. <br>So, how do you think I can achieve this? <br><br>In python instead pyspatialite is compiled againist the same sqlite version <br>used by QGis. I don't know if it's the same for psycopg2, but anyway postgres <br>
API is enough stable.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">I would like to have a<br>
possibility to move/copy layers between various databases, files or<br>
other resources, e.g. drag a WMC layer to RasterLite. </blockquote><div>This is on my gsoc proposal, so don't worry, obviously I will develop it into providers.<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">
IMO the QBrowser<br>
and the PostGIS Manager are very similar. A tree on the left + tools<br>
to work with data. QBrowser currently for OGR,GDAL,GRASS, WMS and<br>
PostGIS Manager for PostGIS. It seems natural to me to merge them into<br>
one tool.<br></blockquote><div>AFAICS looking at the code, in this moment would be easier to merge together <br>QBrowser, RT_Sql_layer, SL_manager and PG_manager in this order, instead <br>of merge them in the opposite way. <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">
The QBrowser / QgsBrowserModel is still work in progress, we don't<br>
have exact ideas how it should look like, it can go in various<br>
directions.<br></blockquote><div>Will it able to do the coffee?? :)<br><br>I'm pretty sure most of you, devs, knows qgis better than me.<br>I hope we could reach enough point of views and re-design all before tomorrow evening, <br>
so the day after tomorrow I can start coding.<br><br>All your opinions and ideas are very welcome.<br>Cheers.<br></div></div><br>-- <br>Giuseppe Sucameli<br>