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

On 8 January 2016 at 07:18, Turunen Tuukka wrote: > > > Hi John, > > > > This item was discussed at Qt Contributor’s Summit, please see session > notes: http://wiki.qt.io/QtCS2015_LTS > > > > For compilers this is also documented to the Qt Base change log: >

[Development] Minimum Deployment Platforms for 5.7 onwards?

Hi, Can I just clarify what the minimum deployment platforms are for 5.7 onwards? That is, the lowest version of each OS that the code must still run on? Far as I can tell it's something like: Windows 7 (or Vista?) Windows Embedded Compact 2013 OSX 10.8 iOS 5.0? Android 4.1 (API Level 16)? RHEL

Re: [Development] How does mktime() handle DST transitions ?

On 3 November 2015 at 14:28, Welbourne Edward < edward.welbou...@theqtcompany.com> wrote: > Hi all, > > I'm looking into QTBUG-49008 and need to work out how diverse > implementations of mktime handle DST transitions: at one end of the year > there's a gap (where 1:59 is followed by 3:00), at the

Re: [Development] QDateTime is missing shared null optimization

[Reply to list this time...] This could work, as Qt::LocalTime / Qt::UTC / Qt::OffsetFromUtc don't actually create or use QTimeZone for anything (at least not yet, LocalTime may yet). I'm assuming dates outside the 1970-4207 year range would still use the d_ptr implementation, as would anything

Re: [Development] Qt Location and Geoclue 2

. And it seems I'm not alone [fedbug]. I searched the web and it seems the work on this has stoped. Does anyone knows the state for this? Thanks in advance, Lisandro. [debbug] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788108 [fedbug] John Layt started working on a Geoclue 2 plugin

Re: [Development] QtCS2014 - Expiring bug reports

On 18 June 2014 07:15, Knoll Lars lars.kn...@digia.com wrote: On 17/06/14 18:31, Robert Löhning robert.loehn...@digia.com wrote: By the way: What will happen to bug reports from now closed identities? The reporter won't get any notification and I'm afraid the watchers won't feel addressed by the

Re: [Development] QtCS2014 - QtPrintSupport Session

On 17 June 2014 03:29, Christian Gagneraud chg...@gna.org wrote: On 14/06/14 05:06, John Layt wrote: While a lot is dependent on me finding time, there are tasks other people could take on, primarily greatly improving our PDF writer support and adding equivalent XPS file format support

Re: [Development] Disable printing support

Em sex 13 jun 2014, às 10:21:08, Massimo Callegari escreveu: I've added QT_NO_PRINTER and QT_NO_PRINTDIALOG to my qmake.conf Qt5 base 5.3.0 still builds fine. libQt5PrintSupport is still created but it's only 43k now. Unfortunately QtWebKit doesn't seem to change in size (I guess cause the

[Development] QtCS2014 - QtPrintSupport Session

Hi, The notes form the QtPrintSupport session are available at https://qt-project.org/groups/qt-contributors-summit-2014/wiki/QtPrintSupport . Basically it's a long list of all the work needing to be done to finish the new print library. While a lot is dependent on me finding time, there are

Re: [Development] Qt 5.3 header diff

On 30 April 2014 16:28, Andrey Ponomarenko aponomare...@rosalab.ru wrote: ABI report for 5.3.0-rc: http://upstream-tracker.org/compat_reports/qt/5.2.1_to_5.3.0-rc/abi_compat_report.html Hi, Interesting that it reports a Medium severity problem for: qpagedpaintdevice.h enum

[Development] Fwd: Proposal: Location hackfest

: Zeeshan Ali (Khattak) zeesha...@gnome.org Date: 2 April 2014 17:00 Subject: Proposal: Location hackfest To: John Layt jl...@kde.org, Aaron McCarthy aaron.mccar...@jollamobile.com, Hanno Schlichting hschlicht...@mozilla.com Cc: Bastien Nocera had...@hadess.net, Ekaterina Gerasimova kittykat3

[Development] Release blocker: printing on OSX 10.9

Hi, Bug report https://bugreports.qt-project.org/browse/QTBUG-38023 is a release blocker as it causes an immediate crash in any Mac app using printing when run as an app bundle on OSX 10.9 Mavericks. It does not crash if the binary is run directly from the command line in 10.9, nor does it crash

[Development] Printing Bug Triage

Hi, I've been doing a bug triage for printing to see what I can close due to the new code, and what high priority issues still need fixing. I've grouped all 177 bugs by linking them to Tasks: QTBUG-37696 QtPrintSupport - Bug Triage QTBUG-25372 QtPrintSupport - CUPS Issues QTBUG-25383

Re: [Development] Current problems in CI

On 13 March 2014 10:06, Sarajärvi Tony tony.saraja...@digia.com wrote: Hi No ETA. There are quite a few problems in the autotest side. Just a minute ago the last try failed. Have to fix more... -Tony Thanks Tony. I guess we won't have it back now before Friday? Just getting a little

Re: [Development] Current problems in CI

On 13 March 2014 18:08, Frederik Gladhorn frederik.gladh...@digia.com wrote: Torsdag 13. mars 2014 16.32.22 skrev John Layt: On 13 March 2014 10:06, Sarajärvi Tony tony.saraja...@digia.com wrote: Hi No ETA. There are quite a few problems in the autotest side. Just a minute ago the last

Re: [Development] Current problems in CI

On 13 March 2014 18:21, John Layt jl...@kde.org wrote: On 13 March 2014 18:08, Frederik Gladhorn frederik.gladh...@digia.com wrote: Looks like we're somewhat back on track. We got a first run for qtbase passing and hopefully start getting the backlog down. Thanks for bearing with us

Re: [Development] Current problems in CI

On 12 March 2014 11:08, Sarajärvi Tony tony.saraja...@digia.com wrote: Hi Currently we are blocking QtBase_dev and qt4. We need to get a fix for an autotest through so that any commit will have a chance to pass the CI. Also, you might have noticed a few problems in the CI with breaking

[Development] Use of resolution in QtPrintSupport.

Hi, [Mostly notes for Andy Shaw to review, but thought I'd post for anyone interested] In QtPrintSupport you can set the resolution to be used in printing, but as with many parts of painting and printing there is confusion and inconsistency between the painting resolution and the physical

Re: [Development] Plans for printing in 5.3 onwards

On Wednesday 12 Feb 2014 15:37:29 John Layt wrote: On Wednesday 12 Feb 2014 12:03:53 John Layt wrote: Sorry, needed to wait until the full stack of changes had been completed and integrated before pushing. The revised patches are up for review, I'm not sure we'll get it done in time

Re: [Development] Plans for printing in 5.3 onwards

On 17 February 2014 14:04, Knoll Lars lars.kn...@digia.com wrote: I¹ve been discussing a bit with Friedemann and Andy on IRC, and I¹m willing to give this change set an exception to the feature freeze. The reason is that I believe that this significantly improves our level of support in this

Re: [Development] Plans for printing in 5.3 onwards

On Monday 10 Feb 2014 17:07:11 Shaw Andy wrote: Since the feature freeze is on the 14th I have been eagerly awaiting the changes that have been indicated already have been done so I can carry on testing. Have I missed some updates or something? I am concerned because I know how many people

Re: [Development] Plans for printing in 5.3 onwards

On Wednesday 12 Feb 2014 12:03:53 John Layt wrote: On Monday 10 Feb 2014 17:07:11 Shaw Andy wrote: Since the feature freeze is on the 14th I have been eagerly awaiting the changes that have been indicated already have been done so I can carry on testing. Have I missed some updates

[Development] Bug fixes to Stable or Dev branch?

Hi, I've seeing contradictory advice on Gerrit as to which branch to push bug- fixes to, some say there will be no 5.2.2 so to use dev instead, others say to keep using stable in case there is. What is the current official policy? Oh, and please remember when making such decisions to clearly

Re: [Development] Plans for printing in 5.3 onwards

On Monday 06 Jan 2014 22:40:44 you wrote: My aims for the 5.3 release will be to * Define the new qpa print device api and implement support for the 3 core platforms * Use this new class in QPrinterInfo and QPrintEngine to replace the current print device code, ensuring behaviour is

[Development] Plans for printing in 5.3 onwards

Hi, I've spent the last few weeks going over the current print support and trying to map out a plan to improve things. We've long intended to create a new QtPrint module to replace QtPrintSupport in which we separate the painting code from the print job management code and support a more modern

Re: [Development] Dropping XP?

On 10 December 2013 16:29, Thiago Macieira thiago.macie...@intel.com wrote: John has one point: he could remove the fallback code for the timezone support. Not for QTimeZone, the Vista stuff only extends the XP support, it doesn't replace it. For QLocale and QCollator we could remove fallback

[Development] Minimum CUPS version vs RHEL 5 support

Hi, I'm refactoring the CUPS printing code (more on that in another email) and noticed we don't currently have a minimum required version set, i.e. we're currently restricted to the 1.0 api released in 1999. CUPS is now at 1.7. There's some nicer api I'd like to use from 1.2 and 1.4, so for Qt

Re: [Development] Dropping XP?

On 9 December 2013 23:23, Thiago Macieira thiago.macie...@intel.com wrote: As Kenneth reminds us[1], Microsoft is ending the security updates for Windows XP in April 2014. That's about when we plan to release Qt 5.3. Should we stop supporting Windows XP? Is there anything we can improve in our

[Development] QTimeZone fixes pushed to Release branch

Hi, I've pushed 4 fixes for QTimeZone to the release branch for review for inclusion in 5.0: 1) https://codereview.qt-project.org/#change,70984 Rather embarrassingly I misspelt the name Olson as Olsen, including in new public api for 5.2. This patch fixes the public api and docs, but doesn't

Re: [Development] Color Management support in Qt 5?

On 9 November 2013 12:50, Olivier Goffart oliv...@woboq.com wrote: On Saturday 09 November 2013 03:02:18 Alessandro Portale wrote: I like the idea of re-starting small, and quite a bit of what was done in Nokia times can certainly be re-used. What if Qt started by simply *enabling* color

Re: [Development] Is possible to remove ICU dependency for Qt5Webkit?

On 5 November 2013 05:09, Yuchen Deng loa...@gmail.com wrote: The ICU dependency is very heavy, I did not like it. Is there any possible to make the ICU depend is optional? Thanks! Sorry, it is not possible to remove the dependency, all you can do is to reduce the size of ICU by not shipping

Re: [Development] QTimeZone (was: Re: Qt 5.2 header diff: QtCore)

On 5 November 2013 12:03, Marc Mutz marc.m...@kdab.com wrote: On Tuesday, November 05, 2013 01:07:32 Thiago Macieira wrote: +// ### Qt 6: Merge with above with default offsetSeconds = 0 +QDateTime(const QDate date, const QTime time, Qt::TimeSpec spec, int offsetSeconds); +#ifndef

[Development] Solaris support in Qt 5?

Hi, Just wondering if anyone knows about the state of Solaris support in Qt 5, or if anyone is actively working on it? Over in KDE we're ripping out some time zone code that currently supports Solaris and I was wondering if I needed to add Solaris tz support in Qt 5? If Qt 5 doesn't even build

Re: [Development] Solaris support in Qt 5?

On 2 November 2013 16:52, Thiago Macieira thiago.macie...@intel.com wrote: On sábado, 2 de novembro de 2013 13:06:43, John Layt wrote: Hi, Just wondering if anyone knows about the state of Solaris support in Qt 5, or if anyone is actively working on it? Over in KDE we're ripping out some

Re: [Development] QtLocation offline Navigation support

On 25 October 2013 15:55, Ramakanthreddy Kesireddy ramakanthreddy.kesire...@techmahindra.com wrote: Hi, Please let me know if there is a plan to enable support for offline Navigation and Map in QtLocation module. Thanks and Regards, Ramakanth Until QtLocation does offer offline maps and

Re: [Development] Where and how does Qt define which platforms are supported?

On 22 October 2013 15:33, Vladimir Minenko vmine...@blackberry.com wrote: The purpose of this email is not to point out something what is not done or wrong. The purpose of this email to initiate a discussion and a work to get this done and create a clear definition where Qt runs on and how

Re: [Development] Calendar Types

On 17 October 2013 19:30, qt...@madagon.com wrote: finally, I'm going to update date time classes to support world calendar types while keeping the binary compatibility. here's an overview of the new changes to be done at this level. Please review and let me know if something wrong.

Re: [Development] Qt Contributors Day

On 22 August 2013 21:24, John Layt jl...@kde.org wrote: Hi, Qt Dev Days Europe is coming up on October 7-9 and once again this year KDE e.V. is partnering with Digia, KDAB and ICS in the running of the event. In particular KDE is once again helping organise a Qt Contributors Day on Monday

Re: [Development] More on QDateTime / QTimeZone

On Saturday 14 Sep 2013 17:11:50 John Layt wrote: As I said, I'm testing a speed-up for toMSecsSinceEpoch() which makes it faster than the old version, which feeds through to most of the other slower functions. I'll also have a look at date() and time() for improvements which will also

[Development] Mac build fails due to qlobal.h being modified?

Hi, I'm trying to do a clean build on Mac of current dev branch, but I keep getting the error: fatal error: file '/Users/odysseus/Development/Qt/src/qt5/qtbase/src/corelib/../../include/QtCore/qglobal.h' has been modified since the precompiled header was built. Any clues on how to fix that

Re: [Development] More on QDateTime / QTimeZone

On Saturday 14 Sep 2013 03:04:45 John Layt wrote: * Rather strangely timeSpec() is 30% slower despite now only returning the member directly instead of having to do a switch based on the member, a few other calls are equally confusing. Ah, stupid me, I was including the creation in the timings

Re: [Development] More on QDateTime / QTimeZone

On Thursday 12 Sep 2013 19:24:15 Knoll Lars wrote: On 9/12/13 9:06 PM, John Layt jl...@kde.org wrote: The first is it means creating a QDateTime becomes a lot slower as we need to calculate the epoch offset up-front, instead of only when/if needed. We might be able to simply cache the time

Re: [Development] More on QDateTime / QTimeZone

On Thursday 12 Sep 2013 22:24:40 Robin Burchell wrote: On Thu, Sep 12, 2013 at 9:24 PM, Knoll Lars lars.kn...@digia.com wrote: We might be able to simply cache the time zone offset once and cache it. Then it should be at the same speed. This would also probably provide hidden wins in

Re: [Development] More on QDateTime / QTimeZone

On Thursday 12 Sep 2013 13:48:24 Thiago Macieira wrote: On quinta-feira, 12 de setembro de 2013 21:06:03, John Layt wrote: * Choose either local msecs or epoch msecs, if epoch then that change can't be done for 5.2 Choose the easiest for you to implement. We're running out of time, so

[Development] More on QDateTime / QTimeZone

Hi, Another QDateTime email. I'm still trying to get a fully working reimplementation of QDateTime as well as the QTimeZone support in for 5.2, but there's a couple of issues outstanding. Storage format / Change of System Time Zone behaviour: My current changes on Gerrit for storing as

Re: [Development] Fwd: Change in qt/qtbase[dev]: Enable -Werror for all of qtbase

-developer-buildOn 4 September 2013 15:21, Poenitz Andre andre.poen...@digia.com wrote: That's wasting our time, as predicted. ../../corelib/tools/qdatetime.cpp: In function 'time_t qt_mktime(QDate*, QTime*, QDateTimePrivate::Spec*, QString*, bool*)':

Re: [Development] Windows: Building QtCore without ICU while still using it for QtWebKit?

On 20 August 2013 08:41, Koehne Kai kai.koe...@digia.com wrote: Is there any way to avoid the ICU dependency in QtCore while still building QtWebKit with it? That would be part of the discussed changes, but it's not there yet. For Qt 5.x, I suggest you configure Qt with '-no-icu', and then

Re: [Development] Status of QTimeZone

On 27 March 2013 20:11, John Layt jl...@kde.org wrote: On 26 March 2013 18:15, Thiago Macieira thiago.macie...@intel.com wrote: On terça-feira, 26 de março de 2013 14.07.56, Sergio Ahumada wrote: As far as I understand, the CI is all in Finland, so GMT +2. In other words, the tests

Re: [Development] Status of QTimeZone

On 26 March 2013 18:15, Thiago Macieira thiago.macie...@intel.com wrote: On terça-feira, 26 de março de 2013 14.07.56, Sergio Ahumada wrote: As far as I understand, the CI is all in Finland, so GMT +2. In other words, the tests are effectively disabled. Yeap, and on all platforms too. I

[Development] Status of QTimeZone

Hi, I've just pushed another set of patches for the QTimeZone and QDateTime changes. The current status is I think the code is now stable enough for a final review and decision on whether to include in 5.1 or not. The QDateTime changes for OffsetFromUTC and the formatter improvements can

[Development] QTimeZone available for review

Hi, I've finally pushed my proposed QTimeZone support to Gerrit for initial review for possible inclusion in 5.1. The reviews are: QLocale - Add private countryToCode() method https://codereview.qt-project.org/50064 QDateTime - Improve and expose Qt::OffsetFromUtc

Re: [Development] ICU and Windows

On Thursday 07 Mar 2013 16:16:05 Koehne Kai wrote: On 02/06/2013 11:20 PM, Koehne Kai wrote: [...] That is what we should do indeed. I learned from http://userguide.icu-project.org/icudata that one can also ship the ICU data in separate .data files, located in a ICU

Re: [Development] [Releasing] Including QTimeZone in Qt 5.1

On Wednesday 27 Feb 2013 13:49:48 Thiago Macieira wrote: On quarta-feira, 27 de fevereiro de 2013 20.57.22, John Layt wrote: Currently is now dropped, we'll wait and see if there's any demand later. It would actually be isDaylightTime(QDateTime::currentMSecsSinceEpoch()). Then please

Re: [Development] [Releasing] Including QTimeZone in Qt 5.1

On Tuesday 26 Feb 2013 16:12:07 Thiago Macieira wrote: On terça-feira, 26 de fevereiro de 2013 22.42.31, John Layt wrote: I'm struggling to think of something different, I can only think of uglies like UnspecifiedTime, NonspecificTime or NotStandardTimeOrDaylightTime. We can't use

Re: [Development] [Releasing] Including QTimeZone in Qt 5.1

On Wednesday 27 Feb 2013 10:26:51 Oswald Buddenhagen wrote: On Tue, Feb 26, 2013 at 04:12:07PM -0800, Thiago Macieira wrote: On terça-feira, 26 de fevereiro de 2013 22.42.31, John Layt wrote: On Wednesday 20 Feb 2013 16:16:55 Thiago Macieira wrote: For 12 commits, I'd just submit

Re: [Development] [Releasing] Including QTimeZone in Qt 5.1

On Wednesday 20 Feb 2013 16:16:55 Thiago Macieira wrote: For 12 commits, I'd just submit straight to dev. Would you prefer it squashed to one big commit, or keep the platform backends separate commits? Except as noted below all other suggested changes are being made. - GenericTime and

Re: [Development] Qt 5.1 feature set and freeze date

On 14 February 2013 19:21, Lorn Potter lorn.pot...@gmail.com wrote: Back long ago https://bugreports.qt-project.org/browse/QTBUG-71 (feel free to assign that one to yourself!) :) Will do :-) I was working on porting qtopia's timezone class to qt. I added full windows olsen conversion.

Re: [Development] Qt 5.1 feature set and freeze date

On Wednesday 13 Feb 2013 08:49:56 Knoll Lars wrote: The detailed timeline will be as follows: * Friday 22. February: If you have a larger feature/feature branch (not yet merged) that you want to have in the release you must have told the release team (by mail to releases@) by then. *

Re: [Development] Qt 5.1 feature set and freeze date

On 13 February 2013 15:13, Koehne Kai kai.koe...@digia.com wrote: Which parts of the ICU data are you using (from http://apps.icu-project.org/datacustom/ ) ? I'd really like us to strip down the default ICU libs on windows for 5.1 ... Good question. I think the following under

Re: [Development] Qt 5.1 feature set and freeze date

On 13 February 2013 18:37, John Layt jl...@kde.org wrote: supplementalData.res timezoneTypes.res windowsZones.res zone/*.res Oh, also looks like: metaZones.res zoneinfo64.res I wish ICU wrote better documentation :-) John

Re: [Development] ICU and Windows

On Friday 11 Jan 2013 13:32:35 Shaw Andy wrote: Since ICU doesn't provide the debug version of the libraries in their binary packages then this means that either the user has to build them themselves (which means modifying the target as well since the output for debug and release defaults to

Re: [Development] Qt Essentials

On 2 August 2012 13:26, Thiago Macieira thiago.macie...@intel.com wrote: On quinta-feira, 2 de agosto de 2012 12.02.45, lars.kn...@nokia.com wrote: I intend to move both Qt 3D and Qt Location out of the essentials list and make them add-ons for now. They are fully usable as-is today, but with

Re: [Development] state of Qt's Australia office

On 1 August 2012 04:00, lorn.pot...@nokia.com wrote: Hi all, We have received word that the Brisbane Australia office, consisting of the teams working on Qt3D, QtDeclarative, QtMultimedia, QtSensors, and QtSystems modules, as well as the CI/QA team for Qt, will be shut down. Our last day

Re: [Development] Color Profile support on Qt

On 1 August 2012 17:56, Olivier Goffart oliv...@woboq.com wrote: On Wednesday 01 August 2012 18:37:14 Stephen Kelly wrote: Given that https://codereview.qt-project.org/#change,31387 has been merged, can you post any more information that will last until the QColorProfile class can be

Re: [Development] Migrating widgets out of qtbase into their own repo

On 4 July 2012 07:03, gunnar.sle...@nokia.com wrote: While on the topic, if we move the widgets, we should also move libQtPrintSupport and libQtOpenGL to their own repositories. That would be nice, but I don't think QtPrintSupport can go as yet as the Mac plugin implementation is actually in

[Development] QtCS - Printing, ICU Locale, Date/Time

Firstly, apologies for missing Day 1 of QtCS, production issues at work prevented me from attending, but I am now on my way for the rest of the event. I hope to run two sessions on either Friday or Saturday, one on Printing, and the other on using ICU in QLocale, which will include plans for

Re: [Development] Qt Mobility in Qt5

On 16 June 2012 08:35, song.7@nokia.com wrote: Thanks… Also do you know how to configure and build the qtpim module along with qtbase ? If you follow the instructions at http://qt-project.org/wiki/Building-Qt-5-from-Git there is a script that does it all for you. John.

Re: [Development] SIC: QAbstractPrintDialog QAbstractPageSetupDialog

On Wednesday 16 May 2012 23:49:42 John Layt wrote: Actually removing the abstract base class is just a case of s/QAbstractPrintDialog/QPrintDialog and tweaking the constructors, as the class is not really abstract, the only virtual method is exec(), nothing else gets reimplemented

Re: [Development] SIC: QAbstractPrintDialog QAbstractPageSetupDialog

On Wednesday 16 May 2012 10:14:27 Thiago Macieira wrote: On quarta-feira, 16 de maio de 2012 00.07.10, John Layt wrote: The QAbstractPritnDialog and QAbstractPageSetupDialog classes are completely unnecessary, are given as bad examples in the Qt API design standards, and were marked

[Development] SIC: QAbstractPrintDialog QAbstractPageSetupDialog

Hi, I want to request a late source incompatible change in QtPrintSupport. The QAbstractPritnDialog and QAbstractPageSetupDialog classes are completely unnecessary, are given as bad examples in the Qt API design standards, and were marked to be merged with QPrintDialog and QPageSetupDialog in

Re: [Development] QtPrintSupport - Platform Support

On Thursday 03 May 2012 20:50:44 Christoph Schleifenbaum wrote: 3 maj 2012 kl. 12:30 skrev Christoph Schleifenbaum: 3 maj 2012 kl. 11:47 skrev Sean Harmer: On Tuesday 01 May 2012 23:21:50 John Layt wrote: snip I've been testing the Mac printing and unfortunately hit a couple

Re: [Development] QtPrintSupport - Platform Support

On Monday 30 Apr 2012 09:06:28 morten.sor...@nokia.com wrote: That would be not possible. QtGui and Widgets loads the Cocoa backend as a plugin and does not link agains it. I think the only options are either duplicating the neccesary code to support QCoreGraphicsPaintEngine in printsupport,

Re: [Development] QtPrintSupport - Platform Support

On Monday 23 Apr 2012 22:17:15 John Layt wrote: For Mac I propose moving QCocoaPrinterSupport into plugins/printsupport/cocoa and moving the private methods from QCocoaNativeInterface to QCocoaPrinterSupportPlugin. I'll do a patch. A harder question is where QMacPrintEngine should

[Development] QtPrintSupport - Platform Support

Hi, While starting to review the current state of QtPrintSupport for Beta 1 and one thing I've immediately noticed is an inconsistency in the platform implementations as to which plugins have which classes where. OSX: src/plugins/platforms/cocoa- QMacPrintEngine

[Development] System Locale Update broken

Hi, QTBUG-24543 reports that the tst_QLocale::windowsDefaultLocale() test is broken and is currently being skipped. I've determined this is because the Qt4 mechanism for triggering a refresh of the Qt system locale whenever the system locale is changed has been removed from

[Development] QLocale private members

Hi, In the QLocale header we have the following code: //private: // this should be private, but can't be struct Data { quint16 index; quint16 numberOptions; }; private: friend struct QLocalePrivate; // ### We now use this field

Re: [Development] qt and printing

On Friday 17 Feb 2012 15:28:49 Francesco R. wrote: Could you (as somebody involved in qt5 planning or development) clarify what the plan are for printing functionality, managment or whatever? Hi Francesco, I'm the new community maintainer for printing support in Qt, so I can fill you in on

Re: [Development] Feature freeze and Alpha

On Sunday 05 Feb 2012 14:12:48 lars.kn...@nokia.com wrote: Is there anything that I have now forgotten that really *must* be in 5.0 (i.e. it really can't be done in a BC/SC way for Qt 5.1)? If you have such an item, please speak up, otherwise I'll consider the above exception list as final.

Re: [Development] QLocale work

On Wednesday 18 Jan 2012 13:21:24 lars.kn...@nokia.com wrote: On 1/18/12 12:35 PM, ext Thiago Macieira thiago.macie...@intel.com On Wednesday, 18 de January de 2012 00.47.31, John Layt wrote: Other classes call public QLocale methods for number symbols like decimalPoint() and negativeSign

Re: [Development] QLocale work

On Monday 16 Jan 2012 23:13:39 Thiago Macieira wrote: I'd say that QLocale should return the information you need. If you need to display that, why shouldn't QLocale provide that info? *Setting* the info is, however, out-of-scope for Qt. When I was discussing it with Denis at QtCS he was

Re: [Development] QLocale work

Splitting up some related issues into separate emails to make it easier for people to address. Which ICU version to use? The latest ICU version is 4.8. See See http://site.icu-project.org/download for detailed release notes. OS X 10.6 shipped with ICU 4.0. The earliest versios of major

Re: [Development] QLocale work

On Sunday 15 Jan 2012 22:53:31 Thiago Macieira wrote: On Sunday, 15 de January de 2012 23.09.35, John Layt wrote: * A QCldrLocale is not really needed for Qt purposes, it's only needed for anyone who wants to know what individual settings are, like KDE What would this class provide

Re: [Development] QLocale work

On Sunday 15 Jan 2012 19:04:09 John Layt wrote: I think I'm favouring the second option as being cleaner and easier to implement in phases. After reading more of the ICU number API and trying some things out, I now think sticking closer to the current model will actually match the ICU API

Re: [Development] QPrintPreview: access to single pages

On Monday 31 Oct 2011 09:37:18 Giovanni Bajo wrote: Hi John, thank you very much for accepting to be the printer maintainer. Last year, we (Develer) proposed a patch that was rejected: http://qt.gitorious.org/qt/qt/merge_requests/733 We then opened a bug to discuss an alternative API to