Re: [QGIS-Developer] Settings migration from QGIS 2 to 3

[Matthias Kuhn]

Add to that

with the new profiles it's super-easy to get a clean slate any time.

Matthias


On 12/8/17 2:31 AM, Nathan Woodrow wrote:
> Hey,
>
> Yes, a dialog is on the todo list just need some time to finish it. 
> Hopefully next monday.
>
> On Fri, Dec 8, 2017 at 11:22 AM, Olivier Dalang
> > wrote:
>
> Hi !
>
> I think the migration should be optional (eg. by displaying a
> message on first start if there's a QGIS2 conf). I'd say this is
> what most programs do for major updates. This would allow users
> who are a bit messy (like me) to take advantage of QGIS3 to make a
> clean start.
>
> Also, you'd be able to easily reset to factory settings by wiping
> the whole QGIS3 directory (actually it's by trying to do that and
> not understanding why the browser kept my providers that I learned
> that config was migrated).
>
> What do you think ? Should I open a feature request ?
>
> Still the feature will definitely be very useful for most users !
> Thank you very much for developing it :)
>
> Olivier
>
>
> On Wed, Nov 1, 2017 at 9:50 PM, Stefan Blumentrath
> >
> wrote:
>
> Thanks so much Alessandro!
>
>  
>
> Having read some documentation:
>
> 
> https://connect.boundlessgeo.com/docs/desktop/1.1.0/system_admins/globalsettings.html
> 
> 
>
> I am sure that this will be a cool new feature in QGIS 3 that
> will be very much appreciated by organisations!!!
>
>  
>
> Thanks again for the hint!
>
>  
>
> Cheers
>
> Stefan
>
>  
>
> *From:*Alessandro Pasotti [mailto:apaso...@gmail.com
> ]
> *Sent:* onsdag 1. november 2017 09.30
> *To:* Stefan Blumentrath  >
> *Cc:* Nathan Woodrow  >; Borys Jurgiel
> >;
> Richard Duivenvoorde  >; qgis-developer@lists.osgeo.org
> 
>
>
> *Subject:* Re: [QGIS-Developer] Settings migration from QGIS 2
> to 3
>
>  
>
>
> Stefan, you may try to use global settings for shared user
> settings, you can specify the global settings file path in
> several ways (and it could even be a shared network folder).
>
> See:
> https://github.com/qgis/QGIS/blob/master/src/app/main.cpp#L131
> 
>
> and:
> https://github.com/qgis/QGIS/blob/master/src/app/main.cpp#L831
> 
>
> the global settings format is exactly the same of the user
> settings file: INI.
>
> Hope this helps.
>
>  
>
>  
>
> On Tue, Oct 31, 2017 at 11:19 PM, Stefan Blumentrath
>  > wrote:
>
> Dear all,
>
>  
>
> I am really looking forward to seeing all QGIS
> configuration in ini-files and that registry will be
> abandoned on Windows in QGIS 3!
>
> That will be a great improvement, esp. from a sys-admin
> perspective!
>
>  
>
> In this consolidation context I was wondering I would be
> possible to prepare for:
>
> -  Use of relative path
> (https://issues.qgis.org/issues/12623
> )
>
> -  Usage of variables in the ini file
>
>  
>
> I have been earlier thinking about “versioning” of ini
> files, so that updates (e.g. changes in OWS URLs) can be
> passed to all users as a sort of “diff/merge” without
> damaging individual adjustments they might have made.
>
> Background is that the Norwegian mapping authority
> provides a “Service feed”
> (https://register.geonorge.no/register/tjenestevarsler
> )
> where all OWS changes are announced… I would love to be
> able to just apply those changes to all our users…
>
>  
>
> No idea if such a thing could be fostered by the way
> settings are stored in the ini files?
>
>  
>
> Cheers
>
> Stefan
>
>  
>
> *From:*QGIS-Developer
>  

Re: [QGIS-Developer] QGIS 3D and Globe plugin

[Nyall Dawson]

On 7 December 2017 at 03:16, Borys Jurgiel  wrote:
> Coming back to your question, Saber... It's no pleasure to drop stuff someone
> spent a lot of time on, but yes, personally +1 for going on.

Mmmm... I'd honestly hope that we don't have that reaction when
dropping code. Every contribution shapes the future codebase, so all
the work done in globe has helped set the direction and framework for
the new 3d stuff. Code churn is natural in a project of this size, and
doesn't reflect lack of value in anyone's past contributions.

> Is anybody here using Globe at all?

I don't -- purely because the build dependencies have never been
satisfied on my OS of choice. However - I don't think removing it is
an option until we have feature parity here, and I'd be reluctant to
remove it even then before having the Qt based 3d stuff exposed to the
wider testing of being included in a stable release.

Martin - do you have a checklist of features in globe which still
require porting to QGIS 3d?

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] Qt 5.10 for QGIS devs - the short story

[Nyall Dawson]

Hi all!

Can't be bothered reading the full changelog of Qt 5.10 which was
released today??! No problem!! Here's the 2 second rundown on changes
which are relevant to us:

- The new QStringView class: cool stuff, but it's no use to us until
we require >= 5.10 and it works correctly with the sip bindings. Let's
revisit in 10 years when debian gets updated.

- QRandomGenerator: useful for us. Maybe we can #ifdef this in for our
various random number generation routines (like in expression
functions) to get better quality random numbers, falling back to the
current routines for < 5.10

- "QImages can now use more than 2GByte of pixel data.". This could
potentially be very good for us, but I can't find any info on whether
the pixel dimension limits have also been lifted (these are what's
blocking us from higher-res/larger composer/map exports).

- "Added AA_DisableWindowContextHelpButton attribute that prevents the
automatic" What's this" button on dialogs on Windows". Woohoo! I
remember discussing somewhere (Nodebo?) about how we could get rid of
all these useless "what's this" buttons on windows dialogs which give
no useful information at all. At the time there wasn't a solution.
https://github.com/qgis/QGIS/commit/15e7d57f adds support for this,
but requires Qt 5.10 windows builds.

- "QDockWidget acquired the ability to be dropped together side by
side". Sounds like a nice little UI benefit we get for free after
moving to 5.10 builds. I'm not sure how useful it will be for QGIS in
practice (I think most users would tend to want less docks visible at
once and more room for the actual map), but it's a nice option to have
available given that it takes no effort on our behalf.

- QtQuick/QML changes: meh. I'll let Matthias get excited about those.
I'm just glad that for once there's a Qt release that includes changes
outside of these modules...

- Qt3D changes: looks like some good stuff here, now that it's of use to us!

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

Re: [QGIS-Developer] Settings migration from QGIS 2 to 3

[Nathan Woodrow]

Hey,

Yes, a dialog is on the todo list just need some time to finish it.
Hopefully next monday.

On Fri, Dec 8, 2017 at 11:22 AM, Olivier Dalang 
wrote:

> Hi !
>
> I think the migration should be optional (eg. by displaying a message on
> first start if there's a QGIS2 conf). I'd say this is what most programs do
> for major updates. This would allow users who are a bit messy (like me) to
> take advantage of QGIS3 to make a clean start.
>
> Also, you'd be able to easily reset to factory settings by wiping the
> whole QGIS3 directory (actually it's by trying to do that and not
> understanding why the browser kept my providers that I learned that config
> was migrated).
>
> What do you think ? Should I open a feature request ?
>
> Still the feature will definitely be very useful for most users ! Thank
> you very much for developing it :)
>
> Olivier
>
>
> On Wed, Nov 1, 2017 at 9:50 PM, Stefan Blumentrath <
> stefan.blumentr...@nina.no> wrote:
>
>> Thanks so much Alessandro!
>>
>>
>>
>> Having read some documentation:
>>
>> https://connect.boundlessgeo.com/docs/desktop/1.1.0/system_a
>> dmins/globalsettings.html
>>
>> I am sure that this will be a cool new feature in QGIS 3 that will be
>> very much appreciated by organisations!!!
>>
>>
>>
>> Thanks again for the hint!
>>
>>
>>
>> Cheers
>>
>> Stefan
>>
>>
>>
>> *From:* Alessandro Pasotti [mailto:apaso...@gmail.com]
>> *Sent:* onsdag 1. november 2017 09.30
>> *To:* Stefan Blumentrath 
>> *Cc:* Nathan Woodrow ; Borys Jurgiel <
>> li...@borysjurgiel.pl>; Richard Duivenvoorde ;
>> qgis-developer@lists.osgeo.org
>>
>> *Subject:* Re: [QGIS-Developer] Settings migration from QGIS 2 to 3
>>
>>
>>
>>
>> Stefan, you may try to use global settings for shared user settings, you
>> can specify the global settings file path in several ways (and it could
>> even be a shared network folder).
>>
>> See:
>> https://github.com/qgis/QGIS/blob/master/src/app/main.cpp#L131
>>
>> and:
>> https://github.com/qgis/QGIS/blob/master/src/app/main.cpp#L831
>>
>> the global settings format is exactly the same of the user settings file:
>> INI.
>>
>> Hope this helps.
>>
>>
>>
>>
>>
>> On Tue, Oct 31, 2017 at 11:19 PM, Stefan Blumentrath <
>> stefan.blumentr...@nina.no> wrote:
>>
>> Dear all,
>>
>>
>>
>> I am really looking forward to seeing all QGIS configuration in ini-files
>> and that registry will be abandoned on Windows in QGIS 3!
>>
>> That will be a great improvement, esp. from a sys-admin perspective!
>>
>>
>>
>> In this consolidation context I was wondering I would be possible to
>> prepare for:
>>
>> -  Use of relative path (https://issues.qgis.org/issues/12623)
>>
>> -  Usage of variables in the ini file
>>
>>
>>
>> I have been earlier thinking about “versioning” of ini files, so that
>> updates (e.g. changes in OWS URLs) can be passed to all users as a sort of
>> “diff/merge” without damaging individual adjustments they might have made.
>>
>> Background is that the Norwegian mapping authority provides a “Service
>> feed” (https://register.geonorge.no/register/tjenestevarsler) where all
>> OWS changes are announced… I would love to be able to just apply those
>> changes to all our users…
>>
>>
>>
>> No idea if such a thing could be fostered by the way settings are stored
>> in the ini files?
>>
>>
>>
>> Cheers
>>
>> Stefan
>>
>>
>>
>> *From:* QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] *On
>> Behalf Of *Nathan Woodrow
>> *Sent:* mandag 30. oktober 2017 15.27
>> *To:* Borys Jurgiel 
>> *Cc:* Richard Duivenvoorde ;
>> qgis-developer@lists.osgeo.org
>> *Subject:* Re: [QGIS-Developer] Settings migration from QGIS 2 to 3
>>
>>
>>
>> Ah right.  I'm happy with whatever there.
>>
>>
>>
>> On Tue, Oct 31, 2017 at 12:25 AM, Borys Jurgiel 
>> wrote:
>>
>> Dnia wtorek, 31 października 2017 00:19:49 Nathan Woodrow pisze:
>> > Hey,
>> >
>> > > There are over 100 keys there, are we going to migrate them all from
>> >
>> > Windows
>> > to windows, like we did with Qgis -> qgis?
>> >
>> > No I don't think we need to do anything for those subgroups, dropping
>> the
>> > Windows placement between version isn't a big deal.  The main core
>> things
>> > to migrate is stuff that is a pain to setup again.
>>
>> Sorry I was unclear. I didn't mean migrating the values, just changing the
>> section for all these keys.
>>
>> Regards,
>> Borys
>>
>>
>>
>>
>> ___
>> 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
>>
>>
>>
>>
>> --
>>
>> Alessandro Pasotti
>> w3:   www.itopen.it
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: 

Re: [QGIS-Developer] Settings migration from QGIS 2 to 3

[Olivier Dalang]

Hi !

I think the migration should be optional (eg. by displaying a message on
first start if there's a QGIS2 conf). I'd say this is what most programs do
for major updates. This would allow users who are a bit messy (like me) to
take advantage of QGIS3 to make a clean start.

Also, you'd be able to easily reset to factory settings by wiping the whole
QGIS3 directory (actually it's by trying to do that and not understanding
why the browser kept my providers that I learned that config was migrated).

What do you think ? Should I open a feature request ?

Still the feature will definitely be very useful for most users ! Thank you
very much for developing it :)

Olivier


On Wed, Nov 1, 2017 at 9:50 PM, Stefan Blumentrath <
stefan.blumentr...@nina.no> wrote:

> Thanks so much Alessandro!
>
>
>
> Having read some documentation:
>
> https://connect.boundlessgeo.com/docs/desktop/1.1.0/system_
> admins/globalsettings.html
>
> I am sure that this will be a cool new feature in QGIS 3 that will be very
> much appreciated by organisations!!!
>
>
>
> Thanks again for the hint!
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* Alessandro Pasotti [mailto:apaso...@gmail.com]
> *Sent:* onsdag 1. november 2017 09.30
> *To:* Stefan Blumentrath 
> *Cc:* Nathan Woodrow ; Borys Jurgiel <
> li...@borysjurgiel.pl>; Richard Duivenvoorde ;
> qgis-developer@lists.osgeo.org
>
> *Subject:* Re: [QGIS-Developer] Settings migration from QGIS 2 to 3
>
>
>
>
> Stefan, you may try to use global settings for shared user settings, you
> can specify the global settings file path in several ways (and it could
> even be a shared network folder).
>
> See:
> https://github.com/qgis/QGIS/blob/master/src/app/main.cpp#L131
>
> and:
> https://github.com/qgis/QGIS/blob/master/src/app/main.cpp#L831
>
> the global settings format is exactly the same of the user settings file:
> INI.
>
> Hope this helps.
>
>
>
>
>
> On Tue, Oct 31, 2017 at 11:19 PM, Stefan Blumentrath <
> stefan.blumentr...@nina.no> wrote:
>
> Dear all,
>
>
>
> I am really looking forward to seeing all QGIS configuration in ini-files
> and that registry will be abandoned on Windows in QGIS 3!
>
> That will be a great improvement, esp. from a sys-admin perspective!
>
>
>
> In this consolidation context I was wondering I would be possible to
> prepare for:
>
> -  Use of relative path (https://issues.qgis.org/issues/12623)
>
> -  Usage of variables in the ini file
>
>
>
> I have been earlier thinking about “versioning” of ini files, so that
> updates (e.g. changes in OWS URLs) can be passed to all users as a sort of
> “diff/merge” without damaging individual adjustments they might have made.
>
> Background is that the Norwegian mapping authority provides a “Service
> feed” (https://register.geonorge.no/register/tjenestevarsler) where all
> OWS changes are announced… I would love to be able to just apply those
> changes to all our users…
>
>
>
> No idea if such a thing could be fostered by the way settings are stored
> in the ini files?
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] *On
> Behalf Of *Nathan Woodrow
> *Sent:* mandag 30. oktober 2017 15.27
> *To:* Borys Jurgiel 
> *Cc:* Richard Duivenvoorde ;
> qgis-developer@lists.osgeo.org
> *Subject:* Re: [QGIS-Developer] Settings migration from QGIS 2 to 3
>
>
>
> Ah right.  I'm happy with whatever there.
>
>
>
> On Tue, Oct 31, 2017 at 12:25 AM, Borys Jurgiel 
> wrote:
>
> Dnia wtorek, 31 października 2017 00:19:49 Nathan Woodrow pisze:
> > Hey,
> >
> > > There are over 100 keys there, are we going to migrate them all from
> >
> > Windows
> > to windows, like we did with Qgis -> qgis?
> >
> > No I don't think we need to do anything for those subgroups, dropping the
> > Windows placement between version isn't a big deal.  The main core things
> > to migrate is stuff that is a pain to setup again.
>
> Sorry I was unclear. I didn't mean migrating the values, just changing the
> section for all these keys.
>
> Regards,
> Borys
>
>
>
>
> ___
> 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
>
>
>
>
> --
>
> Alessandro Pasotti
> w3:   www.itopen.it
>
> ___
> 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-developer] Publishing Custom Python Expression Functions for QGIS

[Stefan Keller]

Hi Nathan

Though QGIS 2.x is end of life soon, can you publish the plugin now
with Simran's fancy new functions (as documented here
https://github.com/NathanW2/qgsexpressionsplus )?

:Stefan

2017-04-10 13:41 GMT+02:00 Khare Simran :
> Hi Nathan,
>
>
> Thanks for your reply. I have now made a pull request to qgsexpressionsplus.
>
>
> Best regards,
>
> Simran
>
> 
> From: Nathan Woodrow 
> Sent: Friday, April 7, 2017 12:52:18 AM
> To: Khare Simran
> Cc: qgis-developer@lists.osgeo.org
> Subject: Re: [Qgis-developer] Publishing Custom Python Expression Functions
> for QGIS
>
> Hey Simran,
>
> Nice work on making some custom expressions.   I'm happy to take a pull
> request for my expressions plus plugin to allow other people to use them.
>
> Send me a PR with the changes and I can merge them for you.
>
> Regards,
> Nathan
>
> On Wed, Apr 5, 2017 at 7:00 PM, Khare Simran  wrote:
>>
>> Hi,
>>
>> I am Simran, an intern at the Institute for Software in HSR Rapperswil. I
>> have come up with some Custom Python Expression functions for QGIS. They
>> are:
>>
>>
>> 1. hstore_get_value(), hstore_exist(), hstore_contains_key_value() and
>> hstore_contains_hstore() :
>>
>> These functions can search for keys and values in hstore strings. They are
>> useful for selecting features based on their tags, which are of hstore type.
>>
>>
>>
>> 2. maxofallvaluesplusone('fieldName')
>>
>> Given a field name, this function returns 1 + the maximum of all values in
>> that field. It is useful for automatically generating a unique id (for
>> example fid) every time the user adds a new feature to a layer.
>>
>>
>> You can find the functions on Github:
>> https://github.com/simran001/custom-expression-functions
>>
>>
>> Please let me know if I should publish these functions as part of the QGIS
>> Resource Sharing Plugin, or if it would be a better idea to make a pull
>> request at https://github.com/NathanW2/qgsexpressionsplus.
>>
>>
>> Thanks!
>>
>>
>> Best regards,
>>
>> Simran
>>
>>
>>
>>
>> ___
>> 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 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] Mac build broken d0e927a

[Gary Sherman]

Larry,

Thanks for th einfo. I’m actually behind the times as usual, using CMake 3.9.1, 
but my build is working now.


> On Dec 5, 2017, at 12:59 PM, Larry Shaffer  wrote:
> 
> Hi Gary,
> 
> Upon a clean build with CMake 3.10.0 (latest in Homebrew since end of 
> November), I get the same error as you reported. I did the following to get 
> back to a working compilation toolchain (assuming you are using CMake from 
> Homebrew): 
> 
> brew rm -f cmake
> 
> # the following is CMake at 3.9.6, with available 'bottled' binaries, i.e. no 
> need to build from source:
> brew install 
> https://raw.githubusercontent.com/Homebrew/homebrew-core/33ed355cfc5ae6c64bb70f80b74876b58d6d413a/Formula/cmake.rb
>  
> 
> 
> # this brings 3.10.0 in again
> brew upgrade cmake
> 
> This leaves you with 3.10.0 'cmake' utility discoverable on PATH (assuming 
> /usr/local/bin is on PATH) and 3.9.6 available from:
> /usr/local/Cellar/cmake/3.9.6/bin/cmake
> 
> You can use `brew switch cmake 3.9.6` if you want 3.9.6 on PATH. I didn't do 
> that, but instead created a new CMake configuration in Qt Creator (assuming 
> you are using that) and applied it to the kit I am using to build QGIS 3. 
> 
> I reported upstream at CMake that this issue has returned:
> https://gitlab.kitware.com/cmake/cmake/issues/17278 
> 
> 
> Regards,
> 
> Larry Shaffer
> Dakota Cartography
> Black Hills, South Dakota
> --
> Boundless Desktop and QGIS Support/Development
> Boundless Spatial - http://boundlessgeo.com 
> lshaf...@boundlessgeo.com 
> On Mon, Dec 4, 2017 at 10:50 AM, Larry Shaffer  > wrote:
> Hi Gary,
> 
> Which CMake version are you using? There is a flaw with CMake 3.9.0 thru 
> 3.9.3 that affects automoc targets, which gave me similar errors:
> https://gitlab.kitware.com/cmake/cmake/issues/17278 
> 
> 
> Works for me with CMake 3.9.4+, using Homebrew dependencies.
> 
> Larry Shaffer
> Dakota Cartography
> Black Hills, South Dakota
> --
> Boundless Desktop and QGIS Support/Development
> Boundless Spatial - http://boundlessgeo.com 
> lshaf...@boundlessgeo.com 
> 
> On Sat, Dec 2, 2017 at 8:44 AM, Gary Sherman  > wrote:
> make[2]: *** No rule to make target 
> `output/lib/qgis_core.framework/qgis_core', needed by 
> `tests/src/core/CMakeFiles/qgis_compositiontest_autogen'.  Stop.
> make[1]: *** [tests/src/core/CMakeFiles/qgis_compositiontest_autogen.dir/all] 
> Error 2
> make: *** [all] Error 2
> 
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
> Gary Sherman
> Founder, QGIS Project
> -Open Source GIS Books:
>  *http://locatepress.com 
> -Geospatial Consulting & Hosting:
>  *http://geoapt.com 
> "We work virtually everywhere"
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
> 
> 
> 
> 
> 
> 
> ___
> 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 
> 
> 

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Gary Sherman
Founder, QGIS Project 
-Open Source GIS Books:
 *http://locatepress.com
-Geospatial Consulting & Hosting:
 *http://geoapt.com
"We work virtually everywhere"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-






___
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] More errors from OS X 10.13 compiling

[Vincent Habchi]

Salut !

> The patch has been added this week according to git blame (maybe a copy/paste)
> In the QT issue tracker, they said the issue has been fixed in Qt 5.4.1 only 
> https://bugreports.qt.io/browse/QTBUG-40449 so we might keep this code.
> 
> I made a PR already in QGIS: https://github.com/qgis/QGIS/pull/5822

Swell. Since MacPorts runs with Qt 5.9, this is fine for me to comment out. 
Thanks for your input.

A finer approach in the code would be to enable/disable the patch according to 
the Qt version QGis gets compiled with, but I’m still skeptical the patch would 
compile with, say Qt 5.3 on OS X 10.13 (has Core Foundation API been changed?).

Bonne soirée et merci !
Vincent

___
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] More errors from OS X 10.13 compiling

[Etienne Trimaille]

The patch has been added this week according to git blame (maybe a
copy/paste)
In the QT issue tracker, they said the issue has been fixed in Qt 5.4.1
only https://bugreports.qt.io/browse/QTBUG-40449 so we might keep this code.

I made a PR already in QGIS: https://github.com/qgis/QGIS/pull/5822

2017-12-07 16:40 GMT+01:00 Vincent Habchi :

> Hey guys,
>
> I’m not sure this has been brought up yet, so here it is:
>
> The fix #11399 doesn’t seem to work on OS X 10.13 anymore or needs further
> patching:
>
> qgslayoutdesignerdialog.cpp:948:11: error: use of undeclared identifier
> 'kCFAllocatorDefault'
>  kCFAllocatorDefault,
>  ^
> qgslayoutdesignerdialog.cpp:950:11: error: use of undeclared identifier
> 'kCFStringEncodingUTF8'
>  kCFStringEncodingUTF8
>  ^
> qgslayoutdesignerdialog.cpp:954:11: error: use of undeclared identifier
> 'kCFAllocatorDefault'
>  kCFAllocatorDefault,
>  ^
> qgslayoutdesignerdialog.cpp:956:11: error: use of undeclared identifier
> 'kCFURLPOSIXPathStyle'
>  kCFURLPOSIXPathStyle,
>  ^
> qgslayoutdesignerdialog.cpp:962:11: error: use of undeclared identifier
> 'kCFAllocatorDefault'
>  kCFAllocatorDefault,
>  ^
> qgslayoutdesignerdialog.cpp:968:22: error: unknown type name 'CFIndex'
>static const CFIndex maxAbsPathCStrBufLen = 4096;
> ^
> qgslayoutdesignerdialog.cpp:973:33: error: unknown type name 'UInt8'
>   reinterpret_cast( [0] ),
>^
> qgslayoutdesignerdialog.cpp:980:7: error: use of undeclared identifier
> 'CFRelease'
>  CFRelease( relCFURL );
>  ^
>
> Also I get this error, in the same file, later:
>
> qgslayoutdesignerdialog.cpp:1263:3: error: use of undeclared identifier
> 'mQgis'
>  mQgis->activateWindow();
>  ^
>
>
> If I disable these patches for MacOS (#if 0 …) the build works, of course.
> Since the first patch is supposed to target a Qt4 bug, can it be safely
> disabled when linking against Qt5?
>
> Thanks,
> Vincent
>
>
>
> ___
> 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] More errors from OS X 10.13 compiling

[Vincent Habchi]

Hey guys,

I’m not sure this has been brought up yet, so here it is:

The fix #11399 doesn’t seem to work on OS X 10.13 anymore or needs further 
patching:

qgslayoutdesignerdialog.cpp:948:11: error: use of undeclared identifier 
'kCFAllocatorDefault'
 kCFAllocatorDefault,
 ^
qgslayoutdesignerdialog.cpp:950:11: error: use of undeclared identifier 
'kCFStringEncodingUTF8'
 kCFStringEncodingUTF8
 ^
qgslayoutdesignerdialog.cpp:954:11: error: use of undeclared identifier 
'kCFAllocatorDefault'
 kCFAllocatorDefault,
 ^
qgslayoutdesignerdialog.cpp:956:11: error: use of undeclared identifier 
'kCFURLPOSIXPathStyle'
 kCFURLPOSIXPathStyle,
 ^
qgslayoutdesignerdialog.cpp:962:11: error: use of undeclared identifier 
'kCFAllocatorDefault'
 kCFAllocatorDefault,
 ^
qgslayoutdesignerdialog.cpp:968:22: error: unknown type name 'CFIndex'
   static const CFIndex maxAbsPathCStrBufLen = 4096;
^
qgslayoutdesignerdialog.cpp:973:33: error: unknown type name 'UInt8'
  reinterpret_cast( [0] ),
   ^
qgslayoutdesignerdialog.cpp:980:7: error: use of undeclared identifier 
'CFRelease'
 CFRelease( relCFURL );
 ^

Also I get this error, in the same file, later:

qgslayoutdesignerdialog.cpp:1263:3: error: use of undeclared identifier 'mQgis'
 mQgis->activateWindow();
 ^


If I disable these patches for MacOS (#if 0 …) the build works, of course. 
Since the first patch is supposed to target a Qt4 bug, can it be safely 
disabled when linking against Qt5?

Thanks,
Vincent



___
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 [1372] PowerPan approval notification.

[noreply]

Plugin PowerPan approval by pcav.
The plugin version "[1372] PowerPan 1.0" is now approved
Link: http://plugins.qgis.org/plugins/powerpan/
___
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] WMS GetFeatureInfo: Test Server with JSON support?

[Matthias Kuhn]

Hi all,

QGIS suppors querying features from a WMS. Among the supported response
formats is JSON.

The current code is based on QScript, which is deprecated.

I've written some code that removes this dependency, so we can stick to
maintained Qt code and can remove a dependency from QGIS.

Now the state is as follows, the code is written, but I couldn't test it
because I don't know a WMS server with this behavior.

If someone could point me towards a server that responds with JSON
formatted feature information, I can make sure, the new code behaves the
way it should.

If not, I'll just keep the old code around on any system that has
QScript available (which should be almost any system out there) and only
resort to the untested code when QScript is not available in the build
environment.

Thanks a lot in advance

Matthias

___
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