Re: [Development] Supported platforms for Qt 5.8

2016-03-02 Thread Petroules Jake
On Feb 19, 2016, at 11:38 PM, Petroules Jake mailto:jake.petrou...@theqtcompany.com>> wrote: * We require the latest Xcode toolchain and OS X on the Mac for compiling (see separate mailing list thread). We support deployment to OS X 10.9 and later (dropping 10.8) +1 * On iOS, w

Re: [Development] Supported platforms for Qt 5.8

2016-02-19 Thread Petroules Jake
On Feb 19, 2016, at 10:58 PM, Andreas Holzammer mailto:andreas.holzam...@kdab.com>> wrote: Hi, What about support for Windows IoT, which might be the successor of WEC. Are there plans to support this? Isn't this implicitly covered under Universal Windows Platform (Windows 10 + WinRT APIs)? T

Re: [Development] Request for a new playground project

2016-02-14 Thread Petroules Jake
Drop the "mobile". Qt is a cross platform project and there does not seem to be any technical reason to restrict this to mobile platforms. So, just "Backend as a Service". On Feb 14, 2016, at 3:54 AM, Guillaume Charbonnier mailto:gcharbonn...@simplisim.net>> wrote: Hi all ! Following my last

Re: [Development] HEADS UP: OSX build requirements for 5.7

2016-02-11 Thread Petroules Jake
Another advantage for end users is that they are guaranteed to get the latest platform features supported by that version of Qt if their OS version also supports them. For example, if Qt is built with the 10.11 SDK and therefore provides a fast WKWebView implementation, users running on 10.11 w

Re: [Development] HEADS UP: OSX build requirements for 5.7

2016-02-10 Thread Petroules Jake
On Feb 10, 2016, at 8:11 AM, Tor Arne Vestbø mailto:tor.arne.ves...@theqtcompany.com>> wrote: On 10/02/16 17:06, Thiago Macieira wrote: On quarta-feira, 10 de fevereiro de 2016 12:00:00 PST Tor Arne Vestbø wrote: Does anyone see any issues with this going forward? We need to be sure Qt compile

Re: [Development] Minimum Deployment Platforms for 5.7 onwards?

2016-01-08 Thread Petroules Jake
o, dropping iOS-6 is a not issue for me, but dropping iOS-7 - yes. jm2c Kind regards, Robert On Fri, Jan 8, 2016 at 12:24 PM, Petroules Jake mailto:jake.petrou...@theqtcompany.com>> wrote: We're raising the minimum OS X to 10.8 (2012). The iOS minimum is still 6 (also 2012), but I wonde

Re: [Development] Minimum Deployment Platforms for 5.7 onwards?

2016-01-08 Thread Petroules Jake
We're raising the minimum OS X to 10.8 (2012). The iOS minimum is still 6 (also 2012), but I wonder whether we should also raise that a version (or even two) considering its uniquely rapid upgrade cycle (frequently upgraded hardware, less user ability to opt out of software updates). Bumping it

Re: [Development] allow Qt for iOS to be built as shared libraries

2015-12-27 Thread Petroules Jake
On Dec 27, 2015, at 2:56 PM, Mike Krus mailto:mike.k...@kdab.com>> wrote: Hi has anybody taken this any further? Just pushed a new patch set which should be mergeable now pending no further complaints. Enabling dynamic builds as frameworks causes link errors. For example, when linking QtNet

Re: [Development] glib's and Qt's RuntimeLocation [OS X]

2015-11-25 Thread Petroules Jake
On Nov 25, 2015, at 12:24 PM, René J. V. Bertin mailto:rjvber...@gmail.com>> wrote: Petroules Jake wrote: [snipped] The only open question is what `macLocation` domain should be returned by QSP::TempLocation: kUserDomain, kSystemDomain or kOnAppropriateDisk . Maybe Jake Petroules a

Re: [Development] glib's and Qt's RuntimeLocation [OS X]

2015-11-25 Thread Petroules Jake
On Nov 25, 2015, at 6:52 AM, René J.V. Bertin mailto:rjvber...@gmail.com>> wrote: Thiago Macieira wrote: >> You're missing a detail. On OS X, $TMPDIR (and QDir::tempPath()) *are* user >> specific. They're also very "immemorable"... > > They're not required to be. If we can detect that they ar

Re: [Development] glib's and Qt's RuntimeLocation [OS X]

2015-11-24 Thread Petroules Jake
On Nov 24, 2015, at 2:25 AM, René J. V. Bertin mailto:rjvber...@gmail.com>> wrote: PS: why did Qt choose ~/Library/Application Support for that location? Isn't the stuff stored there supposed to be volatile that doesn't need to survive reboots or end up in (Time Machine) backups? ~/Library/Appl

Re: [Development] QStandardPaths::writableLocation() on OSX in test mode

2015-11-11 Thread Petroules Jake
On Nov 11, 2015, at 12:21 PM, David Faure mailto:fa...@kde.org>> wrote: On Wednesday 11 November 2015 19:09:58 Petroules Jake wrote: Feel free to do whatever you like for test mode but do not change the existing writable paths. Jake, I would like to understand why you say that. As t

Re: [Development] QStandardPaths::writableLocation() on OSX in test mode

2015-11-11 Thread Petroules Jake
On Nov 11, 2015, at 8:20 AM, René J.V. Bertin mailto:rjvber...@gmail.com>> wrote: On Wednesday November 11 2015 16:03:31 Petroules Jake wrote: I don't understand, what do you mean with "there is only one location"? I mean the API returns a single value, not a list. Howeve

Re: [Development] QStandardPaths::writableLocation() on OSX in test mode

2015-11-11 Thread Petroules Jake
On Nov 11, 2015, at 7:53 AM, René J.V. Bertin mailto:rjvber...@gmail.com>> wrote: On Wednesday November 11 2015 15:32:20 Petroules Jake wrote: No, there is only one location so it must remain /Applications as expected by anyone on the OS X platform. I don't understand, what do yo

Re: [Development] QStandardPaths::writableLocation() on OSX in test mode

2015-11-11 Thread Petroules Jake
On Nov 11, 2015, at 7:13 AM, René J.V. Bertin mailto:rjvber...@gmail.com>> wrote: On Wednesday November 11 2015 15:52:33 David Faure wrote: Cross-posting on Qt's development ML because it seems more than relevant there. To put things in context: this discussion on kde-frameworks-devel was star