Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On terça-feira, 22 de novembro de 2016 05:59:24 PST Marco Bubke wrote: > > I guess GTK maintainers suffer, specially with the last changes they > > announced some time ago about breaking API/ABI (sorry, I don't remember > > exactly which one) in some minor releases. Incindentally the first thing >

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On terça-feira, 22 de novembro de 2016 07:00:17 PST Marc Mutz wrote: > On Tuesday 22 November 2016 02:07:08 Thiago Macieira wrote: > > That said, sometimes rebuilding even if there was no dependency on the > > private API could result in improvements. For example, every time we add > > overloads

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On terça-feira, 22 de novembro de 2016 06:13:44 PST Marco Bubke wrote: > So you say it it does not work because of themeing support? Isn't Qt > Controls 2 not anymore providing them too. And is there no technical > solutions for that? Like propagating the values to the Flatpack themeing > engine.

[Development] CI suffering from an unknown problem

Hi There's something off in the CI currently and we're investigating. -Tony Tony Sarajärvi CI Tech Lead The Qt Company Elektroniikkatie 10 90590, Oulu Finland tony.saraja...@qt.io +358 50 4821416 http://qt.io

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

Marco Bubke wrote: > On November 22, 2016 02:10:50 Thiago Macieira wrote: >> GTK 2 and GTK 3 do keep their ABI just fine. > > To my understanding GTK 3 gives no guarantees at all. That is not true. GTK+ 3 is backwards ABI-compatible with previous versions all the way down to 3.0. There are

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On November 22, 2016 00:47:26 Thiago Macieira wrote: > On segunda-feira, 21 de novembro de 2016 23:18:08 PST Marco Bubke wrote: >> I strongly agree with Andre'. And is a BC break in the time of flat pack >> that bad? As an user I really looking forward to flat pack,

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On November 22, 2016 01:30:47 Lisandro Damián Nicanor Pérez Meyer wrote: > On lunes, 21 de noviembre de 2016 23:18:08 ART Marco Bubke wrote: > [snip] >> And how many applications are Qt only and use no standard lib anyway? Are >> there any numbers? > > Good question, I

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On Tuesday 22 November 2016 02:07:08 Thiago Macieira wrote: > That said, sometimes rebuilding even if there was no dependency on the > private API could result in improvements. For example, every time we add > overloads there's a chance that the new method is faster and will get > selected. Its

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On November 22, 2016 02:10:50 Thiago Macieira wrote: > On segunda-feira, 21 de novembro de 2016 21:30:28 PST Lisandro Damián Nicanor > Pérez Meyer wrote: >> I guess GTK maintainers suffer, specially with the last changes they >> announced some time ago about breaking

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

André Pönitz wrote: > I also said that packagers (i.e. people like you) *are* affected, but I > claimed the way they are affected is not fundamentally different from > what happens if the packages in question uses any other library that > doesn't guarantee BC, or - in case they have similar BC

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

Marc Mutz wrote: > People make mistakes. The difference is that, in the STL, by way of a > larger target audience, mistakes tend to be fewer than in Qt (looked at > qtimageformats, lately?) That is not a fair comparison. The STL has nothing comparable to qtimageformats. Image decoding and

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On lunes, 21 de noviembre de 2016 17:07:08 ART Thiago Macieira wrote: > On segunda-feira, 21 de novembro de 2016 21:33:58 PST Lisandro Damián > Nicanor > Pérez Meyer wrote: > > > I remember in the MeeGo days when building MeeGo with OBS spent an hour > > > on > > > a very beefy machine compiling

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On segunda-feira, 21 de novembro de 2016 21:23:54 PST Lisandro Damián Nicanor Pérez Meyer wrote: > Now I have a question: how will the Qt community take that a distro changes > the SONAME of a lib from, let's say, 5 to 5abi1 when that kind of changes > happen? We prefer to work with downstreams

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On segunda-feira, 21 de novembro de 2016 21:30:28 PST Lisandro Damián Nicanor Pérez Meyer wrote: > I guess GTK maintainers suffer, specially with the last changes they > announced some time ago about breaking API/ABI (sorry, I don't remember > exactly which one) in some minor releases.

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On segunda-feira, 21 de novembro de 2016 21:33:58 PST Lisandro Damián Nicanor Pérez Meyer wrote: > > I remember in the MeeGo days when building MeeGo with OBS spent an hour on > > a very beefy machine compiling Qt, with most of the resources in the OBS > > farm unused because nothing else could

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On lunes, 21 de noviembre de 2016 21:21:08 ART Lisandro Damián Nicanor Pérez Meyer wrote: [snip] > A transition like that would definitely take like a month, in which no other > transition will probably be able to happen because Qt is *so* widely used. Maybe worth mentioning: in order to improve

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On lunes, 21 de noviembre de 2016 15:57:06 ART Thiago Macieira wrote: > On terça-feira, 22 de novembro de 2016 01:06:00 PST André Pönitz wrote: > > I also said that packagers (i.e. people like you) *are* affected, but I > > claimed the way they are affected is not fundamentally different from > >

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On lunes, 21 de noviembre de 2016 23:18:08 ART Marco Bubke wrote: [snip] > And how many applications are Qt only and use no standard lib anyway? Are > there any numbers? Good question, I wonder if there is a way to dig that. > Yes, sometimes they are inlined but sometimes they are > not. Is it

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On lunes, 21 de noviembre de 2016 15:42:12 ART Thiago Macieira wrote: > On segunda-feira, 21 de novembro de 2016 19:36:43 PST Lisandro Damián > Nicanor > Pérez Meyer wrote: > > > So how often do you had a BC break in stdlibc++? > > > > Last time was with gcc5. > > In other words, once in 11

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On martes, 22 de noviembre de 2016 01:06:00 ART André Pönitz wrote: > On Mon, Nov 21, 2016 at 03:49:49PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > > On domingo, 20 de noviembre de 2016 12:53:11 ART André Pönitz wrote: > > [snip] > > > > > - people using Qt in applications distributed

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On terça-feira, 22 de novembro de 2016 01:06:00 PST André Pönitz wrote: > I also said that packagers (i.e. people like you) *are* affected, but I > claimed the way they are affected is not fundamentally different from > what happens if the packages in question uses any other library that > doesn't

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On segunda-feira, 21 de novembro de 2016 23:18:08 PST Marco Bubke wrote: > I strongly agree with Andre'. And is a BC break in the time of flat pack > that bad? As an user I really looking forward to flat pack, so I can > update my heavily used Applications and being not dependent on >

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On segunda-feira, 21 de novembro de 2016 19:36:43 PST Lisandro Damián Nicanor Pérez Meyer wrote: > > So how often do you had a BC break in stdlibc++? > > Last time was with gcc5. In other words, once in 11 years. > And quite messy in some concerns too because they did not increase the > SONAME

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On November 21, 2016 23:57:07 André Pönitz wrote: > On Mon, Nov 21, 2016 at 03:49:49PM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: >> On domingo, 20 de noviembre de 2016 12:53:11 ART André Pönitz wrote: >> [snip] >> > - people using Qt in applications distributed

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On Mon, Nov 21, 2016 at 03:49:49PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > On domingo, 20 de noviembre de 2016 12:53:11 ART André Pönitz wrote: > [snip] > > - people using Qt in applications distributed by packaging > > systems (read "Linux distributions"). They are not affected > >

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On lunes, 21 de noviembre de 2016 19:36:43 ART Lisandro Damián Nicanor Pérez Meyer wrote: > On lunes, 21 de noviembre de 2016 20:47:31 ART Marco Bubke wrote: > > So how often do you had a BC break in stdlibc++? > > Last time was with gcc5. We've got a nice big [transition] within Debian due > to

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On lunes, 21 de noviembre de 2016 20:47:31 ART Marco Bubke wrote: > So how often do you had a BC break in stdlibc++? Last time was with gcc5. We've got a nice big [transition] within Debian due to it. It was related to C++11 stuff, and we've got away precisely because Qt doesn't expose it. And

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 21, 2016 20:02:54 André Pönitz wrote: > On Mon, Nov 21, 2016 at 11:06:52AM +, Edward Welbourne wrote: >> Giuseppe D'Angelo: >> >> I would also like to point out that, despite we have a repository, we >> >> still don't have a tool for properly discussing the

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On Saturday 19 November 2016 21:08:00 Kevin Kofler wrote: > I am glad that I am not alone with that feeling. > > And by the way, with my distribution packager hat on, I have to frown upon > the idea of dragging in yet another dependency just to enforce the C++ > language inventor's personal, not

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

So how often do you had a BC break in stdlibc++? On November 21, 2016 19:50:23 Lisandro Damián Nicanor Pérez Meyer wrote: > On domingo, 20 de noviembre de 2016 12:53:11 ART André Pönitz wrote: > [snip] >> - people using Qt in applications distributed by packaging >>

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Mon, Nov 21, 2016 at 03:29:01PM +0300, Konstantin Tokarev wrote: > > > 21.11.2016, 15:26, "Giuseppe D'Angelo" : > > On Mon, Nov 21, 2016 at 12:58 PM, Oswald Buddenhagen > > wrote: > >>>  Any idea to how to actually make this work? > >>  how about

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Mon, Nov 21, 2016 at 11:06:52AM +, Edward Welbourne wrote: > Giuseppe D'Angelo: > >> I would also like to point out that, despite we have a repository, we > >> still don't have a tool for properly discussing the actual content of > >> QUIPs. > >> > >> * Gerrit does not work because comments

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On domingo, 20 de noviembre de 2016 12:53:11 ART André Pönitz wrote: [snip] > - people using Qt in applications distributed by packaging > systems (read "Linux distributions"). They are not affected > by BC breakages. Users might not notice if we maintainers have to deal with this nightmare.

Re: [Development] Font rendering on X11/Wayland: New FreeType API to toggle LCD filters and stem darkening on a per-font basis, would love a review

> Here is a proof of concept: https://codereview.qt-project.org/#/c/177325/ Oh nice, didn't expect something so soon. Will have a look. > Note, we need a FreeType API for getting to the module-name from the face, or > a direct getter of the stem-darkening on the face. Ah, hm. I only know of a

[Development] HEADS-UP: Branching from '5.8' to '5.8.0' started

Hi, We have started branching from '5.8' to '5.8.0'. Please start using '5.8.0' for new changes targeted to Qt 5.8.0 release. There should be enough time to finalize ongoing changes in '5.8'; final downmerge will happen Monday 28th November. br, Jani

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 21, 2016 14:29:10 Shawn Rutledge wrote: > >> On 21 Nov 2016, at 12:06, Edward Welbourne wrote: >> >> Giuseppe D'Angelo: I would also like to point out that, despite we have a repository, we still don't have a tool for properly

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

> On 21 Nov 2016, at 12:06, Edward Welbourne wrote: > > Giuseppe D'Angelo: >>> I would also like to point out that, despite we have a repository, we >>> still don't have a tool for properly discussing the actual content of >>> QUIPs. >>> >>> * Gerrit does not work

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 21, 2016 13:51:10 Oswald Buddenhagen wrote: > On Mon, Nov 21, 2016 at 01:37:50PM +0100, Marco Bubke wrote: >> On November 21, 2016 12:58:59 Oswald Buddenhagen >> wrote: >> > how about taking the existing processes seriously and

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Mon, Nov 21, 2016 at 01:37:50PM +0100, Marco Bubke wrote: > On November 21, 2016 12:58:59 Oswald Buddenhagen > wrote: > > how about taking the existing processes seriously and exercising social > > pressure on those who think they are above them? > > Sorry, not

Re: [Development] Font rendering on X11/Wayland: New FreeType API to toggle LCD filters and stem darkening on a per-font basis, would love a review

Here is a proof of concept: https://codereview.qt-project.org/#/c/177325/ Note, we need a FreeType API for getting to the module-name from the face, or a direct getter of the stem-darkening on the face. Best regards `Allan ___ Development mailing

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 21, 2016 12:58:59 Oswald Buddenhagen wrote: > On Sun, Nov 20, 2016 at 08:38:50PM +0100, Giuseppe D'Angelo wrote: >> On Thu, Nov 10, 2016 at 12:29 PM, Oswald Buddenhagen >> wrote: >> > the repository has been created. >> >> I

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

21.11.2016, 15:26, "Giuseppe D'Angelo" : > On Mon, Nov 21, 2016 at 12:58 PM, Oswald Buddenhagen > wrote: >>>  Any idea to how to actually make this work? >>  how about taking the existing processes seriously and exercising social >>  pressure on

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Mon, Nov 21, 2016 at 12:58 PM, Oswald Buddenhagen wrote: >> Any idea to how to actually make this work? >> > how about taking the existing processes seriously and exercising social > pressure on those who think they are above them? May I just say that prefer a tool

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Sun, Nov 20, 2016 at 08:38:50PM +0100, Giuseppe D'Angelo wrote: > On Thu, Nov 10, 2016 at 12:29 PM, Oswald Buddenhagen > wrote: > > the repository has been created. > > I would also like to point out that, despite we have a repository, we > still don't have a tool

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Giuseppe D'Angelo: >> I would also like to point out that, despite we have a repository, we >> still don't have a tool for properly discussing the actual content of >> QUIPs. >> >> * Gerrit does not work because comments cannot be threaded, they >> don't stick to multiple reviews, and they can

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Sunday 20 November 2016 20:29:01 Giuseppe D'Angelo wrote: > On Tue, Sep 20, 2016 at 9:27 AM, Thiago Macieira > > wrote: > > Can you remember the list of C++11 features we're allowed to use? We had > > a discussion on the mailing list. > > Going back to this

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On Monday 21 November 2016 09:37:38 Philippe wrote: > > And you think Qt provides what MS added to std::vector here, in QVector? > > Of course not. I just point the danger of dependencies on the usage of STL > APIs, especially corner APIs. > > I understand the #1 target of Qt is to behave the

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

> And you think Qt provides what MS added to std::vector here, in QVector? Of course not. I just point the danger of dependencies on the usage of STL APIs, especially corner APIs. I understand the #1 target of Qt is to behave the same on all platforms (as much as possible...). This is what users

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

On Sunday 20 November 2016 23:20:11 Philippe wrote: > On Sun, 20 Nov 2016 19:49:09 +0100 > > Marc Mutz wrote: > > I just intended to indicate that with 5.0, when we dropped QT_NO_STL, but > > failed to take advantage of the STL containers, > > ...good that STL containers