[QGIS-Developer] Plugins site github warning
FYI: we get a warning from Github for 'moderate severity' issues in our current Django version we use for plugins.qgis.org: https://github.com/qgis/qgis-django/network/alert/REQUIREMENTS.txt/django/open Not sure if we can easily upgrade (I fear we can not), but maybe this is the que to get some people together next week to have a look into this and/or to do some plugins.qgis.org work. Regards, Richard Duivenvoorde ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] MacOS and touchbar
On Fri, 22 Feb 2019, 23:14 Tim Sutton, wrote: > Hi Nyall > > > On 23 Feb 2019, at 01:34, Nyall Dawson wrote: > > Hi list, > > This is just a heads up for any MacOS developers -- there's been some > upstream work recently on Qt and handling the MacOS touchbar. There's > two separate pieces of work here: > > 1. A (proposed) upstream Qt class - QMacTouchBar. Read more here: > https://www.kdab.com/qmactouchbar-has-landed/ > Looks good in that it's intended to be part of the Qt library. > > 2. QtCreator's own implementation of touchbar handling - see > > https://code.qt.io/cgit/qt-creator/qt-creator.git/commit/?id=3c5650e514d6d8bad86a54a037e550db7cc19a71 > This one actually looks a lot nicer then QMacTouchBar, because it > allows for "nested" touchbars based on QAction. > > If any MacOS developers* are motivated, I'd suggest [2] could be > pulled into the QGIS mac native library and used throughout QGIS. > > > I wonder if it is worth spending any effort on this? My experience from > having a Touch Bar on my Mac is that I never use it, and when I do because > I have to (e.g. to adjust volume or brightness), I wish I had keys rather. > Maybe others do find it useful and I am an outlier, but without a ground > swell of eager users, I think we might just be wasting effort (and bloating > out code) on something that users won’t use. > > I love Macs but the Touch Bar == fail for me. > > It took me a while to use it, but I find it very handy for some softwares. The main fail for me is the missing physical esacpe key. But I guess, touch bar was not designed for him users. The other fail is that it's only available for Macbook pro users. I had also a look and was thinking of taking example of Qt Creator's implementation. It would be nice to configure the shortcuts for the touchbar. But as Tim pointed out, it's quite a big effort for a very few users. I was thinking to do this during hackfest. Let's see! > > > > Nyall > > ( * I'm neither a mac user nor a fan of the touchbar concept, so aside > from this heads-up I personally won't be pursuing this further) > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > > > > > --- > > *Tim Sutton* > t...@qgis.org > > > > > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer -- Denis Rouzaud de...@opengis.ch +41 76 370 21 22 ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Plugin [332] geoUmbriaSUIT approval notification.
Right, I'll contact the dev directly. Thanks. Il 23 febbraio 2019 19:26:18 CET, DelazJ ha scritto: >Hi, >It could be nice that the issue report [0] relative to the wrong bug >tracker in metadata gets fixed. > >[0] https://github.com/gmassei/geoUmbriaSUIT/issues > >Regards, >Harrissou > >Le sam. 23 févr. 2019 à 17:43, a écrit : > >> >> Plugin geoUmbriaSUIT approval by pcav. >> The plugin version "[332] geoUmbriaSUIT 3.0.4 Experimental" is now >approved >> Link: http://plugins.qgis.org/plugins/geoUmbriaSUIT/ >> ___ >> QGIS-Developer mailing list >> QGIS-Developer@lists.osgeo.org >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer -- Sorry for being short___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-psc] Request for Change of UserAgent
Hi Richard, I don't think without more information it's clear precisely what QGIS should change to help them? Indeed, personally I'm still not sure what the current problem is for them. I get that they have some over-users of their service and need to curtail this (a very tricky problem), but what's their current solution and how does a user-agent change help it? I'd suggest against QGIS using different user-agents for destinations as was suggested earlier in the thread because down that road lies madness (it's a highly opaque thing that /will/ bite people as they try and debug issues). Cheers, Jonathan On 23/02/2019 11:17, Richard Duivenvoorde wrote: For what I understand, they use some cookie-based trick to help maintain their QOS (and then to make it possible to throttle a very demanding web application?). This made sense to me. Also because I really do not envy maintainers of such services: it is hard to keep up such free services (as an example (see irc log) he mentioned that certain transportation software started to poll the reverse geocoding every second in every car). I think it's pretty important for us to have OSM, and be helpfull to them. But if Firefishy/Grant is willing to give more details (he is in bcc) that would be great. Regards, Richard ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Plugin [332] geoUmbriaSUIT approval notification.
Hi, It could be nice that the issue report [0] relative to the wrong bug tracker in metadata gets fixed. [0] https://github.com/gmassei/geoUmbriaSUIT/issues Regards, Harrissou Le sam. 23 févr. 2019 à 17:43, a écrit : > > Plugin geoUmbriaSUIT approval by pcav. > The plugin version "[332] geoUmbriaSUIT 3.0.4 Experimental" is now approved > Link: http://plugins.qgis.org/plugins/geoUmbriaSUIT/ > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [332] geoUmbriaSUIT approval notification.
Plugin geoUmbriaSUIT approval by pcav. The plugin version "[332] geoUmbriaSUIT 3.0.4 Experimental" is now approved Link: http://plugins.qgis.org/plugins/geoUmbriaSUIT/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1653] CatastroV3 approval notification.
Plugin CatastroV3 approval by pcav. The plugin version "[1653] CatastroV3 1.0 Experimental" is now approved Link: http://plugins.qgis.org/plugins/CatastroV3/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Branch protection enabled for 3.4
great :) Luigi Pirelli ** * LinkedIn: https://www.linkedin.com/in/luigipirelli * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli * GitHub: https://github.com/luipir * Mastering QGIS 2nd Edition: * https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition * Hire me: http://goo.gl/BYRQKg ** On Sat, 23 Feb 2019 at 02:24, Nyall Dawson wrote: > Hi all, > > Just a heads up: now that 3.4 is officially the LTR, I've enabled > github branch protection on the branch. This means all commits to the > branch must now: > 1. Go through a PR > 2. Pass all Travis tests > 3. Be approved by at least 1 other core committer > > (same rules as were in place for 2.18) > > Nyall > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-psc] Request for Change of UserAgent
On 23/02/2019 12.04, Jonathan Moules wrote: > It seems to me there are a few different aspects to this. > > - The convention is to stick "Mozilla 5" into user-agents for browsers > because every other browser uses it. At this point they all pretend to > be each other - > https://stackoverflow.com/questions/1114254/why-do-all-browsers-user-agents-start-with-mozilla > > > - Looking at a bunch of random user-agents, non-browsers don't usually > put "Mozilla" in them (there are websites with long lists). > > - For some reason OSM can't block the QGIS agent. I'm with Mathieu - > this seems odd because it explicitly says "QGIS". > > - Cookies - QGIS doesn't do this (makes sense, doesn't need them), but > why does OSM need them? Relying on cookies alone isn't a good idea - > many users don't allow 3rd party cookies, and many users delete cookies > when the browser closes or even when the tab is closed (self-destructing > cookies plugins). For what I understand, they use some cookie-based trick to help maintain their QOS (and then to make it possible to throttle a very demanding web application?). This made sense to me. Also because I really do not envy maintainers of such services: it is hard to keep up such free services (as an example (see irc log) he mentioned that certain transportation software started to poll the reverse geocoding every second in every car). I think it's pretty important for us to have OSM, and be helpfull to them. But if Firefishy/Grant is willing to give more details (he is in bcc) that would be great. Regards, Richard ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] [Qgis-psc] Request for Change of UserAgent
It seems to me there are a few different aspects to this. - The convention is to stick "Mozilla 5" into user-agents for browsers because every other browser uses it. At this point they all pretend to be each other - https://stackoverflow.com/questions/1114254/why-do-all-browsers-user-agents-start-with-mozilla - Looking at a bunch of random user-agents, non-browsers don't usually put "Mozilla" in them (there are websites with long lists). - For some reason OSM can't block the QGIS agent. I'm with Mathieu - this seems odd because it explicitly says "QGIS". - Cookies - QGIS doesn't do this (makes sense, doesn't need them), but why does OSM need them? Relying on cookies alone isn't a good idea - many users don't allow 3rd party cookies, and many users delete cookies when the browser closes or even when the tab is closed (self-destructing cookies plugins). So I'd suggest it probably is worth removing the "Mozilla" component but it's not clear what the OSM request is about or why, so there's no way to know how to help them solve their problem. Cheers, Jonathan On 21/02/2019 08:13, Richard Duivenvoorde wrote: On 21/02/2019 08.56, Mathieu Pellerin wrote: I would really like to understand (i.e. get an explanation) from the OSM admins as to why a user agent that explicitly identifies itself as QGIS like we have now is not enough for them before moving forward. Being a web admin/developer myself, I can hardly find a reason why that's not enough. I'm more curious than anything else, lots of love to the great OSM guys :) Cc'ing this to Grant/Firefishy too, so maybe he wants to answer here. But one of the things he convinced me with was, that for example in browsers they can work with cookies, while QGIS shows itself as a Mozilla browser, BUT does not accept cookies etc etc. Regards, Richard ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
