<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'><div style="text-align: left;">Hi:<br><br>Thank you Martin to take time to check the design and plans<br>for ogr database access I will keep the classes in app and also<br>I think like you about the architecture for providers, changing to<br>a datasource approach will lead to integrate easily file type layers<br>and datases layers.<br><br>Regards<br>Godofredo Contreras<br></div><br><br><br><hr id="stopSpelling">> Date: Fri, 7 Dec 2007 14:22:55 +0100<br>> From: wonder.sk@gmail.com<br>> To: frdcn@hotmail.com<br>> Subject: Re: Ogr database access design and plans<br>> CC: qgis-developer@lists.qgis.org<br>> <br>> Hi,<br>> <br>> first of all sorry for my late reply.<br>> <br>> I've been thinking quite a lot about the current design and future of<br>> vector providers, database connections etc. The things as you've<br>> designed them can be used well with the current status of QGIS - in<br>> case you will put the new classes to 'app' sources and not to the<br>> libraries.<br>> <br>> My vision is that after 1.0 we should improve our architecture for<br>> providers - and make it more similar to the one used in OGR.<br>> - OGR uses 'data source' for a compound of layers, this can be e.g. a<br>> database or a directory in file system. With data sources you open or<br>> create layers<br>> - QGIS uses 'providers' for accessing directly layers, but there's no<br>> abstraction on the level of data sources as in OGR. With addition of<br>> data sources (which are currently equivalent to database connections<br>> in your design) we will add much more functionality which is not<br>> supported currently by QGIS like some generic way to<br>> list/create/remove/rename etc. layers). This is I guess important part<br>> for our future common Load layer / data manager dialog.<br>> <br>> The future redesign is the reason why I think that the new classes<br>> you're working on should not go to core library. Once your new<br>> features land to trunk, we will be able to reuse the code when<br>> introducing 'data sources' term to QGIS slang. So go ahead with the<br>> coding, we're all looking forward to see the new features in action<br>> :-)<br>> <br>> Regards<br>> Martin<br>> <br>> On Nov 30, 2007 9:16 PM, godofredo contreras <frdcn@hotmail.com> wrote:<br>> ><br>> > Hi Martin:<br>> ><br>> > I have being working with the ogr database access document and modelling<br>> > the classes and interaction needed to enable ogr database access in qgis.<br>> > Attached are a doc document describing the changes planned, the classes<br>> > and dialogs that will be affected and a jpeg image of the model with your<br>> > suggestions<br>> > applied. Could you please give me your comments and suggestions.<br>> ><br>> > Regards<br>> ><br>> > Godofredo Contreras<br>> ><br>> > ________________________________<br>> > Get the power of Windows + Web with the new Windows Live. Power up!<br><br /><hr />You keep typing, we keep giving. Download Messenger and join the i’m Initiative now. <a href='http://im.live.com/messenger/im/home/?source=CRM_WL_joinnow' target='_new'>Join in!</a></body>
</html>