Hi,
I would like to discuss possible change of providers URI format.
Motivation:
- Each provider is using a different way to store additional parameters in URI
- Some providers (WMS) even don't store all parameters in URI and
require extra methods to add a new layer: addRasterLayer(
rasterLayerPat
Hi Radim,
On Wed, May 25, 2011 at 9:37 AM, Radim Blazek wrote:
> I would like to discuss possible change of providers URI format.
> ...
> Some possible solutions:
> 1) minimal:
> - add WMS additional params somehow to URI + parsing in WMS provider
> (it is not clear to me why it was not done thi
On Wed, May 25, 2011 at 1:39 PM, Giuseppe Sucameli wrote:
> An alternative would be use QgsDataSourceURI like a container for QUri, in
> this manner we can define our interface to access the uri informations.
>
In 2 words only, a wrapper class :)
--
Giuseppe Sucameli
Hi Radim
> 1) minimal:
> - add WMS additional params somehow to URI + parsing in WMS provider
> (it is not clear to me why it was not done this way when WMS was
> implemented)
> - encode / decode provider key + uri as single string only for drag and
drop
This is ok as a short term solution.
Hi Radim
On Wed, May 25, 2011 at 2:37 PM, Radim Blazek wrote:
> Some possible solutions:
> 1) minimal:
> - add WMS additional params somehow to URI + parsing in WMS provider
> (it is not clear to me why it was not done this way when WMS was
> implemented)
> - encode / decode provider key + uri
On Wed, May 25, 2011 at 1:39 PM, Giuseppe Sucameli wrote:
> On Wed, May 25, 2011 at 9:37 AM, Radim Blazek
>> Some possible solutions:
>> 1) minimal:
>> - add WMS additional params somehow to URI + parsing in WMS provider
>> (it is not clear to me why it was not done this way when WMS was
>> impl
Hi Radim
> I would suggest a QgsDataSourceURI with two types of params. One type
> whould be set/recognized by a provider to set/get provider specific
> data source URI params, for example setParam(key, val) and
> getParam(key). All parts of URI would be stored as params so that for
> example host
On Wed, Jun 8, 2011 at 2:10 PM, Marco Hugentobler
wrote:
> Hi Radim
>
>> I would suggest a QgsDataSourceURI with two types of params. One type
>> whould be set/recognized by a provider to set/get provider specific
>> data source URI params, for example setParam(key, val) and
>> getParam(key). All
Hi,
after the long discussion when we clarified how to manage URIs well, I
have enabled drag-and-drop from QBrowser to QGIS using the 1) minimal
solution, because of total lack of time. I take the ideas still into
account and I'll return to that later. The feature seems to me quite
important and us
JFYI,
I have extended QgsDataSourceURI with some generic methods setParam,
param, hasParam, encodedUri, setEncodedUri. QUrl is used to
encode/decode the URI.
I have used the new QgsDataSourceURI for WMS so that various WMS
related hacks in QgisApp and QgsRasterLayer, browser etc could be
removed.
10 matches
Mail list logo
