Re: [Qgis-developer] Cleaning up the QEP list

Hi Nathan, no problem. Just wanted to send you some input. Hopefully it helps. You are doing a lot for the project and I understand that during 2.16 you were focused on the styling dock. As always: thanks for your efforts! Andreas On 2016-08-01 01:26, Nathan Woodrow wrote: > Hey Andreas,

[Qgis-developer] Call for proposals: QGIS Grant programme August 2016

Hi All The QGIS project is pleased to announce the first QGIS Grant programme. If you are a developer of community contributor and would like to be funded to work on that great improvement to QGIS that you have been dreaming of, now is your chance! Please visit :

Re: [Qgis-developer] * Important* Preparations for QGIS Developer Meeting in Bonn

Hi, we are now about 30 people on the wiki lists for the hackfest in Bonn and we added some more accomodations to the github wiki: https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint#Registered_Attendees https://github.com/qgis/QGIS/wiki/QGIS-Hackfest---Bonn---August-2016 but I have heard, that

Re: [Qgis-developer] strange GetCapabilities caching

Hi Nicklas, Just a heads up that this is still an issue with 2.16.0; however now it seems to be even worse now: - the "Clear" button for clearing the cache has now been changed to an icon with arrows, that is confusing to the user. I think a button with the words "Clear Cache" makes more

[Qgis-developer] Processing-R multiple fields error

Hi all, a couple of days ago I reported a bug in when creating an R script and one of the input is `ParameterTableMultipleField` [0]. I had a look at the code an maybe I solved a part of the issue, that is the algorithm GUI does not complain anymore. But I'm sill not able to use the outputs of

Re: [Qgis-developer] Report 10 - QGIS Resources Sharing Tools

Hi Akbar, Do you really need a flag? I think you can just check if the scheme is specified in the URI. If it's missing, assume the same protocol. Cheers On 08/01/2016 11:35 AM, Akbar Gumbira wrote: > Hi Matthias, > > I think I missed your point before. I think I will add a flag in the >

Re: [Qgis-developer] Report 10 - QGIS Resources Sharing Tools

Hi Matthias, I think I missed your point before. I think I will add a flag in the metadata that users need to put, to state whether the repository is using the same protocol as the metadata or not. This way it could be more portable to use the repository in different protocol. For example users

Re: [Qgis-developer] Report 10 - QGIS Resources Sharing Tools

Hi Matthias, > I guess support for relative URLs should be trivial and make the > repositories more portable. And as far as I can see it should be > possible to have relative and absolute paths side-by-side, no? If it's a matter of portability, users can still put the metadata inside the

Re: [Qgis-developer] Report 10 - QGIS Resources Sharing Tools

Hi > In general, I feels that this is a better approach also in the sense > that "explicit is better than implicit", we provide explicit URIs > instead of delegate guessing them to the software layer. I guess support for relative URLs should be trivial and make the repositories more portable.

Re: [Qgis-developer] Report 10 - QGIS Resources Sharing Tools

Ok thanks Ale. I'll focus on separating metadata handler and repository handler this week. Cheers On Mon, Aug 1, 2016 at 10:24 AM, Alessandro Pasotti wrote: > On Mon, Aug 1, 2016 at 10:17 AM, Akbar Gumbira > wrote: > >> Hi Ale >> >> >>> Thanks for

Re: [Qgis-developer] Report 10 - QGIS Resources Sharing Tools

On Mon, Aug 1, 2016 at 10:17 AM, Akbar Gumbira wrote: > Hi Ale > > >> Thanks for your report Akbar! >> > > >> I'm sorry if you've not taken into account my repeated calls to keep >> authentication and proxy support in the primary goals. As I explained you >> this is very

Re: [Qgis-developer] Report 10 - QGIS Resources Sharing Tools

On Sat, Jul 30, 2016 at 10:39 PM, Akbar Gumbira wrote: > *What did you get done this week?* > >- *Implemented style resource handler* > > User can now also put style (qml file) in the collection. > > >- *Fixed issues on windows* > > It should be testable now on