[Qgis-developer] OpenLayers Plugin - feature request

Hi, for my own private anjoyment (role playing) I hacked the OpenLayers Plugin to work with Stamen terrain-background. As I think having a background which _only_ consists of physical features might be interesting for other uses, too, I suggest to you to add this to the OpenLayers Plugin. (I

Re: [Qgis-developer] OpenLayers Plugin - feature request

Hi Arne, have a look at the QuickMapServices-plugin. There are already some Stamen backgrounds available. Maybe the one you look for is there too. Have also a look at Settings/More services/Get contributed pack As far as I know, OpenLayers will be replaced by QuickMapServices Chhers Bernd

Re: [Qgis-developer] QGIS 3 - breaking user projects?

As an alternative to building and maintaining a bunch of translation code, how feasible would it be to build something like a python project migration tool? I'm not very familiar with the project XML structure but I'm wondering if it could be done using a python xml library which could update

Re: [Qgis-developer] QGIS 3 - breaking user projects?

On 8 August 2016 at 10:36, Chris Crook wrote: > As an alternative to building and maintaining a bunch of translation code, > how feasible would it be to build something like a python project migration > tool? > > I'm not very familiar with the project XML structure but I'm

Re: [Qgis-developer] QGIS 3 - breaking user projects?

Il 08/08/2016 03:00, Nyall Dawson ha scritto: > On 8 August 2016 at 10:36, Chris Crook wrote: >> As an alternative to building and maintaining a bunch of translation code, >> how feasible would it be to build something like a python project migration >> tool? >> >> I'm not

[Qgis-developer] QGIS 3 - breaking user projects?

Hi all, I'm wondering - what's our stance on breaking users projects for QGIS 3 (in extreme circumstances, obviously)? There's 2 related changes I'd like to make: 1. Kill the old composer attribute table classes: I'd like to kill off the old composer attribute table classes. Here's the