Re: [SailfishDevel] QtLocation | Qt 5.6

sion to not take QtLocation 5.6 into use along with the rest of the Qt >>>>> 5.6 libs was, I believe, because of the different licensing of QtLocation. >>>>> I think veskuh would be the best person to describe our intent going >>>>> forward, and possible roadmap f

Re: [SailfishDevel] QtLocation | Qt 5.6

think veskuh would be the best person to describe our intent going >>>> forward, and possible roadmap for updating. >>>> >>>> Best regards, >>>> Chris. >>>> >>>> >>>> -- >>>>

Re: [SailfishDevel] QtLocation | Qt 5.6

gt; Chris. >>> >>> >>> -- >>> *From:* Devel [devel-boun...@lists.sailfishos.org] on behalf of rinigus >>> [rinigus@gmail.com] >>> *Sent:* Friday, July 07, 2017 6:04 PM >>> *To:* Sailfish OS Developers >>&g

Re: [SailfishDevel] QtLocation | Qt 5.6

el [devel-boun...@lists.sailfishos.org] on behalf of rinigus [ >> rinigus@gmail.com] >> *Sent:* Friday, July 07, 2017 6:04 PM >> *To:* Sailfish OS Developers >> *Subject:* Re: [SailfishDevel] QtLocation | Qt 5.6 >> >> Hi, >> >> it has been rather quiet r

Re: [SailfishDevel] QtLocation | Qt 5.6

] on behalf of rinigus [ > rinigus@gmail.com] > *Sent:* Friday, July 07, 2017 6:04 PM > *To:* Sailfish OS Developers > *Subject:* Re: [SailfishDevel] QtLocation | Qt 5.6 > > Hi, > > it has been rather quiet regarding QtLocation 5.6 during the "first > quarter of 20

Re: [SailfishDevel] QtLocation | Qt 5.6

of rinigus [rinigus@gmail.com] Sent: Friday, July 07, 2017 6:04 PM To: Sailfish OS Developers Subject: Re: [SailfishDevel] QtLocation | Qt 5.6 Hi, it has been rather quiet regarding QtLocation 5.6 during the "first quarter of 2017" (see earlier emails in this thread). I would like to c

Re: [SailfishDevel] QtLocation | Qt 5.6

Hi, it has been rather quiet regarding QtLocation 5.6 during the "first quarter of 2017" (see earlier emails in this thread). I would like to continue my work on navigation/mapping solutions for SFOS and the uncertainty regarding QtLocation is just slowing everything down and lead to major

Re: [SailfishDevel] QtLocation | Qt 5.6

I'd support this, not enough has been coming through at the meeting IMO to have a clear yes/no answer. Best, tortoisedoc On Mon, Jan 9, 2017 at 11:32 PM, Adam Pigg wrote: > I guess we need to wait for the internal review that was mentioned in the > meeting, however it would

Re: [SailfishDevel] QtLocation | Qt 5.6

I guess we need to wait for the internal review that was mentioned in the meeting, however it would be interesting to understand the issues jolla have with particular licenses for software included in sfos. On Mon, 9 Jan 2017 at 21:29 Osmo Salomaa wrote: > On 09.01.2017 13:01,

Re: [SailfishDevel] QtLocation | Qt 5.6

Hi, from reading the meeting transcript it seems that we still don't have straight answer regarding QtLocation 5.6 ("checking at the moment"). However, I don't see the changes in the source code indicating exclusive role of LGPLv3 among LGPL licenses. The LGPLv2.1 license is still there for

Re: [SailfishDevel] QtLocation | Qt 5.6

Hello Slava, On Dienstag, 3. Januar 2017 12:20:55 CET Slava Monich wrote: > Qt 5.6 is coming with the next update. Those modules that can't be > upgraded due to licensing restrictions will stay at 5.2. Oh, that sounds frustrating. Is that an official Jolla information? Best, micu -- OpenPGP /

Re: [SailfishDevel] QtLocation | Qt 5.6 - alternatives (PinchMap)

Hello Martin, On Dienstag, 3. Januar 2017 20:44:38 CET Martin Kolman wrote: > There are other - possibly less convenient but Jolla Store copamatible - > ways of showing a map on Sailfish OS than Qt Location. Thank you very much for for sharing this comprehensive information! It is very

Re: [SailfishDevel] QtLocation | Qt 5.6 - alternatives (PinchMap)

Thanks for sharing, great info! BR, // Pete Martin Kolman kirjoitti tiistai 3. tammikuuta 2017: > Mon, 02 Jan 2017 01:09:49 + Helicalgear .: > > Hi, > > > > Qt5.2 itself provided the "QtLocation" as you see. > > But, unfortunately, QtLocation is not allowed to use for 3rd party > > apps

Re: [SailfishDevel] QtLocation | Qt 5.6 - alternatives (PinchMap)

Mon, 02 Jan 2017 01:09:49 + Helicalgear .: Hi, Qt5.2 itself provided the "QtLocation" as you see. But, unfortunately, QtLocation is not allowed to use for 3rd party apps officially, right now. Please see "Sailfish FAQ" https://harbour.jolla.com/faq#QML_API And the list of modules which

Re: [SailfishDevel] QtLocation | Qt 5.6

The writer probably intented "to use a library" as "to copy code from a library"; Duh. On Tue, Jan 3, 2017 at 2:08 PM, Tone Kastlunger wrote: > Ah! Slava, the article you pointed at is wrong; > > Quoting : > > "The same incompatibility issue exists with LGPLv2.1

Re: [SailfishDevel] QtLocation | Qt 5.6

Ah! Slava, the article you pointed at is wrong; Quoting : "The same incompatibility issue exists with LGPLv2.1 projects that want to use an LGPLv3 library. They *must* be upgraded to LGPLv3. " This statement is not true for LGPLv3, but for GPLv3 (according to FSF's compatibility matrix at

Re: [SailfishDevel] QtLocation | Qt 5.6

Doesnt Qt Provide the choice for GPLv3 / LGPLv3? >From the FSF compatibility matrix http://gplv3.fsf.org/dd3-faq it appears that only using GPLv3 library code in LGPLv2 and LGPLV2.1 is cause for trouble (=forced upgrade to GPLv3); but LGPLv3 seems ok. That said, this has been viewed with eyes

Re: [SailfishDevel] QtLocation | Qt 5.6

I'm not a lawyer but apparently something is fundamentally wrong with LGPLv3. This sounds similar to what I heard about it: http://nmav.gnutls.org/2013/03/the-perils-of-lgplv3.html -Slava Even more detailed view : http://www.ics.com/blog/changes-qt-licensing On Tue, Jan 3, 2017 at 11:58

Re: [SailfishDevel] QtLocation | Qt 5.6

Even more detailed view : http://www.ics.com/blog/changes-qt-licensing On Tue, Jan 3, 2017 at 11:58 AM, Tone Kastlunger wrote: > Weird, > http://doc.qt.io/qt-5/licensing.html from here only MIT / BSD-Style > licenses are mentioned. > Where's the issue there? > >

Re: [SailfishDevel] QtLocation | Qt 5.6

Weird, http://doc.qt.io/qt-5/licensing.html from here only MIT / BSD-Style licenses are mentioned. Where's the issue there? tortoisedoc On Tue, Jan 3, 2017 at 11:46 AM, Rinigus wrote: > Morning, > > Slava, would you mind to check out which licensing terms prevent >

Re: [SailfishDevel] QtLocation | Qt 5.6

Morning, Slava, would you mind to check out which licensing terms prevent QtLocation specifically? Or maybe someone else knows specifics? Is there any hope that the situation would change in future? I wonder whether all platforms are hit by it or whether Ubuntu Touch complies with the new

Re: [SailfishDevel] QtLocation | Qt 5.6

As far as I understand, QtLocation license terms have changed and that prevents it from being upgraded to 5.6 which is its first stable release. That's why it's not allowed and won't be allowed even after the rest of Qt is upgraded to 5.6. Qt 5.6 is coming with the next update. Those modules

Re: [SailfishDevel] QtLocation | Qt 5.6

Also if built as an android app it cannot be run on any third-party SFOS ports (nexus 5 one plus X etc) which do not have the Android app layer. On Mon Jan 2 05:33:21 2017 GMT-0500, Tone Kastlunger wrote: > There goes android then. No SFOS. Kinda defyes the point IMO :/. > > On Mon, Jan 2, 2017

Re: [SailfishDevel] QtLocation | Qt 5.6

There goes android then. No SFOS. Kinda defyes the point IMO :/. On Mon, Jan 2, 2017 at 11:18 AM, Kaj-Michael Lang wrote: > On Mon, 2017-01-02 at 09:05 +, Peter Pykäläinen wrote: > > That is an option yes, but a bit of a cheat :) > > Or even more of a filthy and dirty cheat,

Re: [SailfishDevel] QtLocation | Qt 5.6

Well I do not know if you can call it "cheat" when Jolla itself suggests for it :P On Mon, Jan 2, 2017 at 11:05 AM, Peter Pykäläinen < peter.pykalai...@gmail.com> wrote: > That is an option yes, but a bit of a cheat :) > > Tone Kastlunger kirjoitti maanantai 2. tammikuuta 2017: > > Bundle it as

Re: [SailfishDevel] QtLocation | Qt 5.6

We should be allowed to use at least all the same components Jolla itself is using. Talk about vibration etc. Those have been in the SFOS from the beginning and are still not allowed in 3rd party apps. Kinda lame. // Peter Pykäläinen 2017-01-02 11:18 GMT+02:00 Kaj-Michael Lang :

Re: [SailfishDevel] QtLocation | Qt 5.6

On Mon, 2017-01-02 at 09:05 +, Peter Pykäläinen wrote: > That is an option yes, but a bit of a cheat :) Or even more of a filthy and dirty cheat, build it instead as a QtQuick Component 2 Android app and you can use the latest version Qt (My Android app built on 5.7.0 runs nicely). But yeah,

Re: [SailfishDevel] QtLocation | Qt 5.6

That is an option yes, but a bit of a cheat :) Tone Kastlunger kirjoitti maanantai 2. tammikuuta 2017: > Bundle it as a private dependency? > > On Mon, Jan 2, 2017 at 10:50 AM, Peter Pykäläinen < > peter.pykalai...@gmail.com> wrote: > > > In my opinion we've waited long enough already. Jolla

Re: [SailfishDevel] QtLocation | Qt 5.6

Bundle it as a private dependency? On Mon, Jan 2, 2017 at 10:50 AM, Peter Pykäläinen < peter.pykalai...@gmail.com> wrote: > In my opinion we've waited long enough already. Jolla should really > consider to allow more modules if they want better apps. > > // Pete > > helicalgear . kirjoitti

Re: [SailfishDevel] QtLocation | Qt 5.6

In my opinion we've waited long enough already. Jolla should really consider to allow more modules if they want better apps. // Pete helicalgear . kirjoitti maanantai 2. tammikuuta 2017: > Hi, > > Qt5.2 itself provided the "QtLocation" as you see. > But, unfortunately, QtLocation is not

Re: [SailfishDevel] QtLocation | Qt 5.6

Hi, Qt5.2 itself provided the "QtLocation" as you see. But, unfortunately, QtLocation is not allowed to use for 3rd party apps officially, right now. Please see "Sailfish FAQ" https://harbour.jolla.com/faq#QML_API And the list of modules which can be used by 3rd party apps.

[SailfishDevel] QtLocation | Qt 5.6

Hello Sailors! As I already told you, I am working on the Berlin Vegan guide for SailfishOS: Recently, I added a map feature to the app: