Re: [Development] [Releasing] Qt 5.13.0 released
On Thursday, 20 June 2019 13:20:24 PDT Lisandro Damián Nicanor Pérez Meyer wrote: > > I'm also deprecating QResource::isCompressed(): > > https://codereview.qt-project.org/c/qt/qtbase/+/265835 > > this patch is proposed for 5.13.1, but reviewers may ask that it be pushed > > back to 5.14, as 5.13.0 is released. > > I don't think it will hurt. And adding API to QResource for 5.14 (something it should have always had...): https://codereview.qt-project.org/c/qt/qtbase/+/265850 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Releasing] Qt 5.13.0 released
On Thu, 20 Jun 2019 at 13:54, Thiago Macieira wrote: > > On Thursday, 20 June 2019 09:29:53 PDT Thiago Macieira wrote: > > Anyway, I think the simplest is that we change rcc's default to zlib, so we > > don't compress with zstd unless asked for. > > https://codereview.qt-project.org/c/qt/qtbase/+/265834 Thanks! > Can you ask that distributions backport this patch if they turn on zstd? I'm > not subscried to the distributions ML. Sure thing, mail sent. > I'm also deprecating QResource::isCompressed(): > https://codereview.qt-project.org/c/qt/qtbase/+/265835 > this patch is proposed for 5.13.1, but reviewers may ask that it be pushed > back to 5.14, as 5.13.0 is released. I don't think it will hurt. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] How to port from Q_FOREACH to range-based for
On Thu, Jun 20, 2019 at 08:44:40AM +, Frederik Gladhorn wrote: > On tirsdag 11. juni 2019 09:48:00 CEST Lars Knoll wrote: > > > On 11 Jun 2019, at 09:35, Olivier Goffart wrote: > > > > > > On 11.06.19 09:17, Lars Knoll wrote: > > > > > >> So, is removing it worth all the hassle to us and our users? Q_FOREACH is > > >> a macro and it doesn’t really cost us anything to keep it around. Yes, > > >> it has issues with non Qt containers and I wouldn’t recommend it for any > > >> new code. But maybe we could simply fix that part, but making Q_FOREACH > > >> emit a compiler warning if used on a container that’s not implicitly > > >> shared? > > > > > > > > +1 > > > Although we should probably still discourage its usage in the > > > documentation. > > > > Regarding the compiler warning: > > > > > > https://codereview.qt-project.org/c/qt/qtbase/+/244010 > > > > > > > > > > > > Nice. So doesn’t this solve most of the issues we have with Q_FOREACH (maybe > > with the exception that some people find macros ugly)? > > Yes, I'd also be happy about changes to the docs, Yes, > let's really not encourage new uses of foreach. But I think we'd do > ourselves and especially our users a disfavor by deprecating it. Yes, and yes. > I have seen enough bugs introduced by people fixing deprecation warnings > blindly, Yes. > and there seem to be so many issues when it comes to foreach that I > think it's simply not worth it. And yes. > Frederik > > (I hope q_foreach continues its long career in the shade, relaxing and slowly > fading from public memory...) And yes. And now something feels odd. But I think I can get used to that. Andre' ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Releasing] Qt 5.13.0 released
On Thursday, 20 June 2019 09:29:53 PDT Thiago Macieira wrote: > Anyway, I think the simplest is that we change rcc's default to zlib, so we > don't compress with zstd unless asked for. https://codereview.qt-project.org/c/qt/qtbase/+/265834 Can you ask that distributions backport this patch if they turn on zstd? I'm not subscried to the distributions ML. I'm also deprecating QResource::isCompressed(): https://codereview.qt-project.org/c/qt/qtbase/+/265835 this patch is proposed for 5.13.1, but reviewers may ask that it be pushed back to 5.14, as 5.13.0 is released. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Releasing] Qt 5.13.0 released
On Thursday, 20 June 2019 04:03:03 PDT Lisandro Damián Nicanor Pérez Meyer wrote: > Actually the KDE people advised the contrary: > > > https://mail.kde.org/pipermail/distributions/2019-June/000321.html Ok, would've been nice if someone made that recommendation two days ago. Or a month ago, when we started the betas. Anyway, I think the simplest is that we change rcc's default to zlib, so we don't compress with zstd unless asked for. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Releasing] Qt 5.13.0 released
Hi! El mié., 19 jun. 2019 12:35, Thiago Macieira escribió: > On Wednesday, 19 June 2019 03:59:29 PDT Jani Heikkinen wrote: > > I am happy to announce we have released Qt 5.13.0 today. Please read more > > information from Lars's release blog post: > > https://blog.qt.io/blog/2019/06/19/qt-5-13-released/ > > > > Once again big thanks to everyone involved! > > Linux distributions are advised to add a BuildRequires: libzstd-dev (or > equivalent) to their package management software). Yocto Project recipes > should also be updated to add that. > Actually the KDE people advised the contrary: https://mail.kde.org/pipermail/distributions/2019-June/000321.html > Linux distributions that ensure the XDG shared-mime-info package is always > installed can save 320 kB in QtCore by compiling with > -no-mimetype-database. > You save 90 kB if you add libzstd but not this option. > Thanks for this tip! ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] [Announce] Qt Creator 4.10 Beta released
We are happy to announce the release of Qt Creator 4.10 Beta! https://blog.qt.io/blog/2019/06/20/qt-creator-4-10-beta-released/ -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Announce mailing list annou...@qt-project.org https://lists.qt-project.org/listinfo/announce ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] How to port from Q_FOREACH to range-based for
On tirsdag 11. juni 2019 09:48:00 CEST Lars Knoll wrote: > > On 11 Jun 2019, at 09:35, Olivier Goffart wrote: > > > > On 11.06.19 09:17, Lars Knoll wrote: > > > >> So, is removing it worth all the hassle to us and our users? Q_FOREACH is > >> a macro and it doesn’t really cost us anything to keep it around. Yes, > >> it has issues with non Qt containers and I wouldn’t recommend it for any > >> new code. But maybe we could simply fix that part, but making Q_FOREACH > >> emit a compiler warning if used on a container that’s not implicitly > >> shared? > > > > > +1 > > Although we should probably still discourage its usage in the > > documentation. > > Regarding the compiler warning: > > > > https://codereview.qt-project.org/c/qt/qtbase/+/244010 > > > > > > > Nice. So doesn’t this solve most of the issues we have with Q_FOREACH (maybe > with the exception that some people find macros ugly)? Yes, I'd also be happy about changes to the docs, let's really not encourage new uses of foreach. But I think we'd do ourselves and especially our users a disfavor by deprecating it. I have seen enough bugs introduced by people fixing deprecation warnings blindly, and there seem to be so many issues when it comes to foreach that I think it's simply not worth it. Frederik (I hope q_foreach continues its long career in the shade, relaxing and slowly fading from public memory...) > Cheers, > Lars > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
