<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;"><br></div>Hi Marco:<br><br>I was looking into your patch for postgis dialog and I noticed that in qgsdbsourceselectbase.ui <br>the encoding combobox is missing. It wont be used anymore?<br><br>Regards<br>Godofredo Contreras<br><br><br><hr id="stopSpelling">> From: marco.hugentobler@karto.baug.ethz.ch<br>> To: qgis-developer@lists.qgis.org<br>> Date: Sat, 29 Dec 2007 16:43:16 +0100<br>> Subject: Re: [Qgis-developer] extensions to postgis dialog<br>> <br>> Hi all,<br>> <br>> Here is the patch that adds a tree view and options for table search to the <br>> postgis dialog. Please test it and report bugs and/or comments.<br>> <br>> There are two new classes derived from Qt model in this patch. One is the base <br>> model and the second one a proxy model that adds the capability of filtering <br>> according to wildcard or regexp. <br>> <br>> cheers,<br>> Marco<br>> <br>> Am Freitag 14 Dezember 2007 13:44:12 schrieb Marco Hugentobler:<br>> > Hi Godofredo and Tim,<br>> ><br>> > Thanks for your feedback. So I'll make a patch for svn head with the<br>> > proposed extensions.<br>> ><br>> > > Could I suggest using Qt model/view for this - whever list become lone<br>> > > I think the model / view approach will always be more efficient. It<br>> > > also has QSortFilterProxModel by which you can easily add sorting and<br>> > > filtering.<br>> ><br>> > This is a good idea. QSortFilterProxModel will certainly help me with<br>> > filtering.<br>> > Reading through the Qt documentation, the model/view concept seems to be a<br>> > very flexible way of accessing and displaying data. In a way, the qgis<br>> > vector data provider is also a model.<br>> ><br>> > > I was going to suggest also that we create src/models and src/views<br>> > > for any custom models and views we create.<br>> ><br>> > As models are always non-gui related and views are dialogs, would it make<br>> > sense to have src/core/models and src/app/views?<br>> ><br>> > >I think is a good idea, but how could we deal with databases that donīt<br>> > > use schemas<br>> > >like mysql? maybe in this case we could place all tables into public<br>> > > schema.<br>> ><br>> > Also possible would be to introduce a schema name "" (empty string)<br>> > or "default". I suppose you just ignore the schema name when accessing<br>> > mysql databases?<br>> ><br>> > Regards,<br>> > Marco<br>> ><br>> > On Thursday 13 December 2007 17:03:20 Tim Sutton wrote:<br>> > > Hi<br>> > ><br>> > > Could I suggest using Qt model/view for this - whever list become lone<br>> > > I think the model / view approach will always be more efficient. It<br>> > > also has QSortFilterProxModel by which you can easily add sorting and<br>> > > filtering.<br>> > ><br>> > > http://doc.trolltech.com/4.3/qsortfilterproxymodel.html#details<br>> > ><br>> > > I was going to suggest also that we create src/models and src/views<br>> > > for any custom models and views we create.<br>> > ><br>> > > Regards<br>> > ><br>> > > Tim<br>> > ><br>> > > 2007/12/13, Hugentobler Marco <marco.hugentobler@karto.baug.ethz.ch>:<br>> > > > Hi,<br>> > > ><br>> > > > The list of tables in the postgis connection dialog may become quite<br>> > > > long for users that have a lot of tables and views. I therefore would<br>> > > > like the following extensions:<br>> > > ><br>> > > > -Convert the table widget to a tree widget. For every schema, there<br>> > > > would an item that can be expanded/collapsed and contains the<br>> > > > tables/views of the schema. Like this, there will be much better<br>> > > > overview in situations with many schemas/tables/views.<br>> > > ><br>> > > > -Add a line edit that takes regular expressions and, if not empty,<br>> > > > displays only the entries where the table name matches the regular<br>> > > > expression.<br>> > > ><br>> > > > Are there any objections or suggestions to this?<br>> > > > Godofredo, does this fit together with the work you are doing in the<br>> > > > ogr-plugin-branch and shall I code the dialog extensions also into this<br>> > > > branch?<br>> > > ><br>> > > > Regards,<br>> > > > Marco<br>> > > ><br>> > > ><br>> > > > _______________________________________________<br>> > > > Qgis-developer mailing list<br>> > > > Qgis-developer@lists.qgis.org<br>> > > > http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-developer<br>> <br>> <br>> <br>> -- <br>> Dr. Marco Hugentobler<br>> Institute of Cartography<br>> ETH Zurich<br>> Technical Advisor QGIS Project Steering Committee<br><br /><hr />Get the power of Windows + Web with the new Windows Live. <a href='http://www.windowslive.com?ocid=TXT_TAGHM_Wave2_powerofwindows_012008' target='_new'>Get it now!</a></body>
</html>