Re: [Development] New survey roll-out on doc.qt.io

[Florian Bruhin]

Hey,

> Thanks for the information,
> 
> it took me a while to notice it was a banner,
> so for anyone wondering, here's the direct link:
> https://www.surveymonkey.com/r/M59K58P

Note the banner has the current page name as an URL parameter, which
presumably gets stored alongside with the survey responses.

Without that context, half of questions in there don't make sense:

- "Did you find the information you were looking for on this page?"
- "What information were you looking for on this page?"
- "How understandable did you find the content on this page?"

Florian

> 
> Cheers
> 
> On 5/2/24 2:58 PM, Safiyyah Moosa via Development wrote:
> > Hi All
> > 
> > The Documentation team has launched a new survey on doc.qt.io. Help us 
> > to improve our documentation by filling out the survey and letting us 
> > know your thoughts!
> > 
> > Kind Regards,
> > Safiyyah Moosa
> > 
> > 
> > Kind Regards,
> > 
> > Safiyyah Moosa
> > 
> > Bsc Electronic Engineering
> > 
> > Documentation Engineer
> > 
> > Qt Group
> > Sandakerveien 116
> > 0484 Oslo
> > Norway
> > 
> > _safiyyah.moosa@qt.io_
> > 
> > +47 47794451
> > 
> > _www.qt.io _
> > 
> > https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black.png
> >  
> > https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right_2023-03-01-095511_zhlr.png
> >    
> > https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png
> >     
> > https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png
> >    
> > https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png
> >  
> > 
> > 
> 
> -- 
> Dr. Cristian Maureira-Fredes
> Senior R&D Manager
> 
> The Qt Company GmbH
> Erich-Thilo-Str. 10
> D-12489 Berlin
> 
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin,
> Registergericht: Amtsgericht
> Charlottenburg, HRB 144331 B
> --
> -- 
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development


signature.asc
Description: PGP signature
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Behavior-changing bugfixes in patch-level releases

[Florian Bruhin]

Hey,

> We do generate release notes for patch release, i.e.
> https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.5.1/release-note.md
> where this particular change is included in the “Important Changes”
> section:
> https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.5.1/release-note.md#qtdeclarative
> 
> The intention of those notes is to make it easier for people upgrading
> to evaluate the impact, and to decide whether some extra testing needs
> to be done before rolling the new version out to everyone.
> 
> But maybe this is not the most effective way to communicate changes
> like this. Are these notes easy enough to find? Is a single “Important
> Changes” section sufficient, or do we need more differentiation? Some
> important changes are marked as such because they fix a bad bug,
> others might be marked as important because they might require
> adaptation in existing code that relies on previous behavior. They are
> all marked as "Important Behavior Change” in the commit log, and
> usually with a module or even type name (in this case,
> "[ChangeLog][QtQuick][ListView][Important Behavior Change]”). Our
> commit template suggests “[ChangeLog][module][class/topic]”.
> 
> Perhaps the release-notes generation script could group things a bit
> better, at least by module rather than by repository, and also
> including the class/topic.
> 
> Ideas on how we can make this better are very welcome.

It's a tiny change, but personally I'd appreciate if the titles of the
"Important changes" entries were formatted in bold. It'd make things a
bit easier to scan visually, as that's all you need to get a first
impression of "does this affect me in any way?".

As for discoverability, I see it's linked in the release blog post.
Perhaps it could also be listed in the release announce mails for people
who don't click through to the blog post?

Finally (not sure if that's already done), for people upgrading using
the installer, maybe the installer could link to the release notes or
even show them inline?

But in the end, I suppose many people (don't necessarily mean the OP
here, just in general) just won't read them. Not much you can do about
that, I think.

Florian


pgphithimlpzS.pgp
Description: PGP signature
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Help me, check bug Qt topic 142770, very urgent!

[Florian Bruhin]

Hi,

On Tue, Feb 14, 2023 at 09:38:43AM +0100, g.scarpe...@u-tech.it wrote:
> Can you help me to resolve the problem illustrated in the discussion
> with topic 142770 ?

This is a community mailinglist, which is the wrong place to get
"very urgent" help with a non-public bug. Most people here (me included)
won't even be able to see the thing you mention.

Florian

-- 
m...@the-compiler.org | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Licensing of qtbase

[Florian Bruhin]

Hi,

(The usual "I am not a lawyer" disclaimer applies.)

On Wed, Jul 13, 2022 at 12:14:27PM +0200, Felix Crazzolara wrote:
> I would like to use Qt for a personal project. In my project, I use a
> relatively small part of Qt and I think that the components of QtBase here
> https://github.com/qt/qtbase suffice for my application.

If you don't redistribute your project, you don't need to care much
about licenses.

If you do redistribute it, do so under a license compatible with the
GPLv3, and you will be fine.

> I read about the Qt licensing model on the official website. What surprised
> me now to see, is that there are quite a few licenses in the LICENSES
> folder in the repository referred to above. Among them is for example an
> MIT license.
> 
> How can I understand this? Is the QtBase component of Qt itself licensed
> with an MIT license? Can I choose which license in the LICENSES folder to
> use if I restrict myself to QtBase?

The Licenses folder contains *all* licenses used in the project,
including those of third-party components.

The license which actually applies is specified on a per-file level,
e.g. here: https://github.com/qt/qtbase/blob/dev/src/corelib/io/qurl.cpp#L3

https://www.qt.io/product/features?hsLang=en#js-6-3 lets you see the
individual components of Qt and what license they are available as.

Most of Qt is available under the LGPL (or commercial), some of it under
the GPL (or commercial). For qtbase, I *think* it should all be LGPL
even, but don't quote me on that.

For a quick overview, here is what I found in the Qt 6.4 qtbase repo, by
running this and then some manual editing:

$ git grep -ho "SPDX-License-Identifier: .*" | sort | uniq -c | sort -nr
   3478 SPDX-License-Identifier: LicenseRef-Qt-Commercial OR LGPL-3.0-only OR 
GPL-2.0-only OR GPL-3.0-only
   1797 SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GPL-3.0-only WITH 
Qt-GPL-exception-1.0
   1591 SPDX-License-Identifier: LicenseRef-Qt-Commercial OR BSD-3-Clause
(those seem to be code snippets in the documentation)
359 SPDX-License-Identifier: LicenseRef-Qt-Commercial OR 
GFDL-1.3-no-invariants-only
(example code apparently?)
 46 SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GPL-3.0-only
  3 SPDX-License-Identifier: MIT
  1 SPDX-License-Identifier: LicenseRef-Qt-Commercial OR
  1 SPDX-License-Identifier: BSL-1.0
  1 SPDX-License-Identifier: BSD-3-Clause
  1 SPDX-License-Identifier: Apache-2.0 OR MIT
  1 SPDX-License-Identifier: Apache-2.0

For an opensource project, even more so for a small personal one, I'd
recommend licensing it under the GPLv3 and you should be all set.

Florian

-- 
m...@the-compiler.org | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Freenode's IRC

[Florian Bruhin]

Hi,

On Wed, May 19, 2021 at 04:17:49PM +0200, Giuseppe D'Angelo via Development 
wrote:
> While Freenode won't shut down tomorrow morning, this still raises some
> questions whether Qt wants to keep its community there or move to another
> network.

Well, turns out it did shut down some channels essentially overnight,
including #qtwebengine and my project's channel (#qutebrowser):

05:03 -> freenodecom (~com@freenode/staff) has joined #qtwebengine
05:03 -- freenodecom has changed topic for #qtwebengine from
"QtWebEngine | https://wiki.qt.io/QtWebEngine |
qtwebeng...@qt-project.org - Channel now recreated on
irc.libera.chat" to "This channel has moved to ##qtwebengine. The
topic is in violation of freenode policy:
https://freenode.net/policies";
05:03 <@freenodecom> This channel has been reopened with respect to
the communities and new users. The topic is in violation of freenode
policy: https://freenode.net/policies
05:03 <@freenodecom> The new channel is ##qtwebengine
05:03 <- freenodecom (~com@freenode/staff) has left #qtwebengine

They now claim this has "accidentally" targetted more channels than they
intended, but this kind of power abuse (mixed with incompetence) is not
tolerable either way, in my eyes.

Here's my take on it, FWIW:
https://blog.qutebrowser.org/qutebrowser-moving-to-libera-chat.html

Florian

-- 
m...@the-compiler.org | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Moving IRC from Freenode to Libera.Chat, voting thread

[Florian Bruhin]

Hi,

On Sat, May 22, 2021 at 03:06:28AM +0200, Giuseppe D'Angelo via Development 
wrote:
> This is EXCLUSIVELY asking whether to transfer the official IRC presence of
> Qt Project channels from Freenode (current) to Libera.Chat.

+1.

I'll answer to the other thread with some context.

Florian

-- 
m...@the-compiler.org | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] off the list

[Florian Bruhin]

Hey,

On Fri, Nov 27, 2020 at 08:45:02AM -0500, w wrote:
> I don't know how I got on this list but someone better take me off it 

Every mail you get from this mailinglist has a footer:

> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development

At the bottom of that website, there's a form where you can unsubscribe
yourself.

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Issues with latest Qt6 snapshot on Windows

[Florian Bruhin]

On Fri, Jul 24, 2020 at 09:19:40AM -0400, Tristan Millns wrote:
> Take me off this list. 

Every mail you get from the list has a footer, with a link to the lists
website:

Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

You can unsubscribe yourself there.

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] QtWebEngine and Qt 6 (was: Re: Can your module be included in Qt 6?)

[Florian Bruhin]

Hey,

On Fri, Jun 26, 2020 at 09:53:55AM +, Lars Knoll wrote:
> As you can see, the scope of 6.0 will be reduced compared to 5.15.

So now that it's official that QtWebEngine won't be part of Qt 6.0:

What will that mean for security upgrades (i.e. updates of the underlying
Chromium) for open source users of Qt as soon as Qt 6.0 is out?

Given that the 5.15 LTS is restricted to commercial users[1], does that mean
that open source projects will be stuck on Qt 5.15.4 (or .3 or .5 or whatever)
until Qt 6.1 is released in May/June 2021 or so?

If that's the case, I'm not sure that'll help Qt's reputation when it comes to
its handling of security issues... Don't get me wrong, I can understand where
TQtC is coming from with the commercial-only LTS decision - but if there are no
QtWebEngine security fixes for open source users at all for what's probably
more than half a year (the time between the last 5.15.x before 6.0; and 6.1),
that seems like a huge problem, no?

I'm all for "We are making this change to encourage open-source users to
quickly adopt new versions" (from that blog post), but what if that's not
possible because those new versions don't exist at the point the old versions
get abandoned? Wouldn't it make a lot of sense to make the 5.15 LTS
commercial-only only at the point Qt 6.1 is released, at least for all modules
not part of Qt 6.0?

[1] https://www.qt.io/blog/qt-offering-changes-2020

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qt Multimedia as Add-on in Qt 6

[Florian Bruhin]

On Fri, May 22, 2020 at 02:54:24PM -0400, Matthew Woehlke wrote:
> On 22/05/2020 13.43, Jason H wrote:
> > How about I just pay - which my company already does? The lagging mobile
> > support has us considering moving away from Qt. I think this decision
> > would confirm our direction and only hasten our departure
> > from the Qt ecosystem.
> > 
> > I guess to some degree it depends on how you define "essential".
> > Clearly multimedia *is* essential
> What's "clear" to you may not be "clear" to everyone. I, personally, don't
> believe I have ever used QtMM. I can think of applications I might *like* to
> write that might use it, but plenty of applications I *do* write have no
> need for it. Most KDE applications don't need it. QtC and Designer don't
> need it.
> 
> In fact, out of the software I use in a typical day, the only stuff that
> comes to mind that might need it are:
> 
> - Gwenview (but it's more a nice-to-have)
> - Plasma? (Whatever is responsible for system notifications, anyway)
> - My web browser (except I use Firefox, which does not use Qt...)
> - Dragon
> 
> Really, the only three things I would argue *need* it are my web browser,
> media player, and the desktop environment itself.
> 
> For quite a few application developers, it is *not* essential at all.

FWIW I write a browser[1] using Qt - in its default configuration, it uses
QtWebEngine, which does not use QtMultimedia either (and uses Chromium's
multimedia stack instead).

Florian

[1] https://www.qutebrowser.org/

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed; Qt 5.15.0 Changes Files

[Florian Bruhin]

On Mon, Apr 20, 2020 at 10:42:37AM +, Fabian Kosmale wrote:
> webengine is on page 2 as far as I can tell.

Ah, I didn't see the page switcher. Nevermind then, my bad!

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed; Qt 5.15.0 Changes Files

[Florian Bruhin]

On Mon, Apr 20, 2020 at 09:44:01AM +, Jani Heikkinen wrote:
> Hi,
> Initial ones here: 
> https://codereview.qt-project.org/q/message:%2522Add+changes+file+for+Qt+5.15.0%2522
> 
> Please finalize asap,we should get these in before RC (which is coming at the 
> end of April)

Is it intended that qtwebengine is missing there?

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] GitHub Pull requests

[Florian Bruhin]

On Thu, Mar 12, 2020 at 10:51:31PM -0700, Thiago Macieira wrote:
> I also need two CIs so I can test on just three OSes.

Can you elaborate on that? I assume those are Linux, macOS and Windows?

Pretty much all big CI providers I can think of (Travis CI, AppVeyor,
GitHub Actions, Azure Pipelines) support all three of those.

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] GitHub Pull requests

[Florian Bruhin]

Hi,

On Tue, Mar 10, 2020 at 05:08:39PM +, Zacruzin via Development wrote:
> Please remove me from this email chain.Thank you!

On the bottom of every mail you find a footer, liking to the website for this
mailinglist:

> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development

You can unsubscribe yourself there.

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] (no subject)

[Florian Bruhin]

Emily, Jenifer,

Every post to this list has a link to the list information page in the footer:

On Fri, Jan 31, 2020 at 12:02:25PM +, Emily Kaizer wrote:
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development

You can unsubscribe at the bottom of that page.

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Qt offering

[Florian Bruhin]

On Wed, Jan 29, 2020 at 05:22:04PM -0500, Matthew Woehlke wrote:
> On 29/01/2020 17.13, Konstantin Shegunov wrote:
> > On Wed, Jan 29, 2020 at 11:55 PM Matthew Woehlke wrote:
> >> We need more open-source-meets-kickstarter...
> > 
> > ehm, Patreon?
> 
> Aside from issues with Patreon's reputation, there's a reason I wrote
> "kickstarter". I can't think of any instance where I've seen tangible
> rewards for supporting *an open source project* via Patreon. Conversely,
> Kickstarter offers *specific* rewards of the payee's choice, and often
> involves some sort of public "thank you" (which I don't think I've
> *ever* seen with Patreon).
> 
> Besides, I was thinking more along the lines of something that could
> integrate with other OSS tools (e.g. GitHub).
> 
> I want a "proud sponsors" page. I want to be able to offer bounties for
> specific bugs or feature requests. (IOW, read the rest of my previous
> message that you didn't quote.)

FWIW I've done both Indiegogo/Kickstarter (i.e. one-time funding) and GitHub
Sponsors (recurring funding, perhaps unsurprisingly, integrated with GitHub)
with my project:

https://www.indiegogo.com/projects/qutebrowser-a-keyboard-focused-vim-like-browser#/
https://www.kickstarter.com/projects/the-compiler/qutebrowser-v10-with-per-domain-settings
https://github.com/sponsors/The-Compiler

The problem with one-time fundings is that you usually need some tangible new
shiny feature to be funded, while - at least in my case - the area needing most
work is what's generally necessary but not very appealing to oudsiders (i.e.
general maintenance).

I offer physical rewards (like stickers/shirts) in return of longer recurring
contributions, though some things (e.g. t-shirts) I'll only order once.

I'm pretty sure there are other projects with some kind of reward - though not
necessary physical things, as those often are one-person projects where the
developer might not want the additional work.

Here are some more examples with Patreon FWIW:
https://reference.kemitchell.com/top-donations-developers.html

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qt 5.13 & 5.14 add device-independent pixels to device-dependent

[Florian Bruhin]

On Tue, Jan 28, 2020 at 07:14:50PM -0800, Thiago Macieira wrote:
> I don't know what makes KMail different. I thought it was the use of a 
> qtwebengine window, but the qtwebengine examples seem to work fine.

FWIW I've had issues (and so had other qutebrowser users) with context menus
appearing in a wrong place or not at all for as long as I remember with
QtWebEngine. There have been various fixes in that direction, but as of Qt
5.14, I still see it happening. Unfortunately, I've never found a way to
consistently reproduce it and it happens relatively rarely.

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Qt offering

[Florian Bruhin]

Hey,

On Mon, Jan 27, 2020 at 04:00:48PM +, Tuukka Turunen wrote:
> After the change every release of Qt will look like a non-lts release for
> open-source users. Think of Qt 5.14 as an example. It was released in
> December. Today it received the first patch release. There will be more
> before next feature release is out. For open-source user Qt 5.15 will look
> just like Qt 5.14 does.

Except that the next release after Qt 5.15 won't be 5.16 but Qt 6.

How does the transition story for open source projects look there? If the
(security) support for Qt 5.15 is dropped as soon as Qt 6 is released, does
that mean projects would have to migrate immediately? What if they are using
third-party libraries which need to be migrated first?

I'm aware that Qt 5 -> Qt 6 is supposed to be a manageable change (and smaller
than 3 -> 4 or 4 -> 5). But still, expecting projects to essentially have
migrated before Qt 6 is released isn't exactly realistic...

Am I missing something there?

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Updated high-DPI support for Qt 5.14

[Florian Bruhin]

Hey,

On Mon, Sep 16, 2019 at 07:43:29AM +, Paul Tvete wrote:
> On Friday, 13 September 2019 17:14:32 CEST Thiago Macieira wrote:
> 
> > What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
> 
> QT_AUTO_SCREEN_SCALE_FACTOR was deprecated in 2016. The recommended 
> replacement is QT_ENABLE_HIGHDPI_SCALING. 

Huh? How come the documentation (even for 5.14) still mentions that and doesn't
mention QT_ENABLE_HIGHDPI_SCALING at all then?

https://doc-snapshots.qt.io/qt5-5.14/highdpi.html

I guess with "in 2016" you mean the change this email is talking about:
https://codereview.qt-project.org/c/qt/qtbase/+/176381

That commit was merged for Qt 5.14 a couple of weeks ago, not in 2016:

  commit 1de8b01d2b6db8a4fe2eddd0c595d9e680964db5
  Author: Morten Johan Sørvig 
  AuthorDate: Thu Nov 10 14:17:53 2016 +0100
  Commit: Morten Johan Sørvig 
  CommitDate: Fri Aug 23 03:41:14 2019 +0200

Looks like that change didn't add a changelog entry and didn't bother to update
the documentation at all...

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Save the date: Qt Contributors Summit 2019 is 19th - 21st November in Berlin

[Florian Bruhin]

Hey Tuukka,

On Thu, Sep 05, 2019 at 11:23:28AM +, Tuukka Turunen wrote:
> We are working on getting the registration open in the coming weeks as well
> as more details of the planned structure.

I don't mean to be pushy, but is there any chance you could share a more exact
location already, if that's set?

I'd like to take care of accommodation ASAP since I plan to come to Berlin
before Qt World Summit already and stay until Qt Contributors summit, so it'd
be good to know where in Berlin :)

Thanks!

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Gerrit is back / email template changed

[Florian Bruhin]

On Tue, May 28, 2019 at 02:17:19PM +, Frederik Gladhorn wrote:
> If someone has other ideas, we can discuss them!

On a related note - I'm a bit confused about the ellipsis in the subject. Why
"Change in ...qtgamepad[5.12.4]:" and not just "Change in qtgamepad[5.12.4]:"?

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Proposal: Using Gerrit for new approver proposals?

[Florian Bruhin]

Hi,

As someone who's following this list but not working at the Qt Company, I find
the stream of "+1" emails when there's a new proposal for approval rights for
someone a bit noisy :)

What about using Gerrit to do so? I'm not sure how the repository would look
(probably just text files with the proposal text)? Then people could +1 that
change instead.

Just my $0.02 - it's not like I'd unsubscribe over this :)

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes planned for the online installer

[Florian Bruhin]

On Mon, Mar 25, 2019 at 07:22:59AM +, Tuukka Turunen wrote:
> This would be a good opportunity to recommend everyone to contact your local
> "ftp server" providers and ask if they could mirror Qt. We do not have any
> mirror in Australia, for example. We do have quite nice amount of mirrors,
> but there is always room for more: https://download.qt.io/static/mirrorlist/ 

FWIW I've asked https://mirror.init7.net/ in Switzerland - let's see what they
think :)

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] About our CI update notifications

[Florian Bruhin]

Hi,

On Thu, Mar 15, 2018 at 08:26:21AM +, Tony Sarajärvi wrote:
> How does this sound to you recipients of these e-mails? Enough or would this 
> be excess spam to some degree?

That sounds like useful information to me.

However, I'm wondering: Would it be possible to display some kind of
announcement banner on Gerrit instead of (or in addition to) the mails?
That way, people would get that information right where they need it
(when using Gerrit or trying to stage a change).

I'm just a somewhat casual contributor though, I don't know how well
that'd fit people's workflows - just my $0.02 ;-)

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt branches & proposal how to continue with those

[Florian Bruhin]

On Mon, Jan 29, 2018 at 02:32:58PM +0100, Kevin Kofler wrote:
> Simon Hausmann wrote:
> > In the light of that, I think it would be better to keep the LTS branches
> > open longer and stop doing patch releases for minor releases that are not
> > LTS.
> 
> -1 from a distro packager perspective. LTS just does not fit together with 
> fast-moving distributions, and we really need those bugfix releases for the 
> branches we ship.
> 
> Especially QtWebEngine requires those bugfix releases for security fixes, 
> and tracking LTS is not that great there because the base Chromium gets old 
> pretty quickly, and websites start complaining (e.g., Google already 
> complains about 5.9 being an outdated Chromium) or even stop working 
> altogether. The frequency of LTS releases has also so far been totally 
> insufficient to keep up with Chromium security fixes (see the huge amount of 
> time – almost a whole year! – between 5.6.2 and 5.6.3).
> 
> I would rather see LTS canceled and more effort put into the current 
> releases, if having both is a problem.

I can't agree more - while I'm not a distro packager, I'm a maintainer
of an opensource project[1] using QtWebEngine.

5.x.0 releases are often quite painful, as they're full of regressions
introduced because of new Chromium versions. I try to find report those
as soon as possible, but there are always issues ([2] for an example)
which only surface after a release.

Like Kevin said, of course security updates are also a big issue, and
only getting them all 6 months is definitely not good...

Florian

[1] https://www.qutebrowser.org/
[2] https://bugreports.qt.io/browse/QTBUG-65223

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 5.10 beta 4 released

[Florian Bruhin]

Hi,

(not sure which ML this fits on, so I removed releasing@ - please Cc me on
replies as I only get development@ as digest)

On Fri, Nov 10, 2017 at 01:01:17PM +, Jani Heikkinen wrote:
> Current plan is to release Qt 5.10 rc next Thu as planned so please make sure
> all blockers from blocker list
> (https://bugreports.qt.io/issues/?filter=18957) is fixed immediately. Also
> make sure all open release  blockers are really visible in the list...

Would it be possible to add https://bugreports.qt.io/browse/QTBUG-63388 there?
It's a regression from 5.9 and makes dozens of tests in my projects' testsuite
fail, to the point that it's hard to check whether there are other unrelated
failures.

There's a fix at https://codereview.qt-project.org/#/c/208595/ which didn't
make it through CI so far - I just want to make sure it doesn't miss the
release ;)

Florian

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Viktor Engelmann for Approver Status

[Florian Bruhin]

On Tue, Jul 11, 2017 at 11:25:21AM +, Simon Hausmann wrote:
> I'd like to propose Viktor for approver status. Since August last year he's 
> been contributing to QtWebEngine full-time. Based on my experience talking to 
> him and working with him, I trust him to review changes thoroughly and 
> approve or reject changes responsively.

I'm "just" an occasional outside contributor, but a big +1 from me too :)

Florian

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QtWebKit is coming back

[Florian Bruhin]

* Lars Knoll  [2016-06-07 06:38:35 +]:
> Ok, in this case a separate repo is maybe a better strategy.
> WebKitQt (as Allan proposed) might be a good name in this case :)

I don't want to start any bike-shedding here, but if there's a
QtWebKit and a WebKitQt and those are *basically* different versions
of the same thing, that sounds like a source for a lot of confusion...

FWIW the unofficial name it just happened to get in various related
IRC channels is "QtWebKit-NG" ;)

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QT development needed

[Florian Bruhin]

* Jim Stracka  [2015-12-15 13:44:17 -0800]:
> I have an iOS App that I need written in QT for porting to other platforms.
> 
> the iOS App is "StrackaLine"

This list is for development *of* Qt itself.

As for your question, I suggest you take a look at Qt's partners:
http://www.qt.io/partners/

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] New Qt5.6 Beta snapshot available

[Florian Bruhin]

* anton  [2015-12-14 19:11:15 +0100]:
> So if I understand right,
> in a Qt Widgets Application I can no more embed 
> a Html/Browser component anymore.

You can use QtWebEngine instead which is the successor of QtWebKit,
and based on Chromium:

http://wiki.qt.io/QtWebEngine

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] toLower() vs. toCaseFolded()

[Florian Bruhin]

* Marc Mutz  [2015-12-09 12:20:36 +0100]:
> On Wednesday 09 December 2015 10:57:21 Florian Bruhin wrote:
> > * Marc Mutz  [2015-12-09 11:54:54 +0100]:
> > > Hi,
> > > 
> > > http://doc.qt.io/qt-5/qstring.html#toCaseFolded is very vague on what
> > > case folding actually _is_ and how it's different from toLower().
> > > 
> > > Can someone please tell me the difference and why toCaseFolded() exists
> > > in the first place? Is it faster? Is it guaranteed to not make the
> > > string longer/shorter?
> > 
> > Maybe http://www.w3.org/International/wiki/Case_folding helps?
> 
> Not really. Neither does it patch our docs... :)

I'm going to say it - the overhead a small doc contribution really
discourages me from doing so. I'm tired of waiting[1] for reviews,
having to ping people again, and then fighting with the CI (though
that part is getting better).

Florian

[1] 
https://codereview.qt-project.org/#/q/owner:%22Florian+Bruhin+%253Cqt-project.org%2540the-compiler.org%253E%22+status:open,n,z

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] toLower() vs. toCaseFolded()

[Florian Bruhin]

* Marc Mutz  [2015-12-09 11:54:54 +0100]:
> Hi,
> 
> http://doc.qt.io/qt-5/qstring.html#toCaseFolded is very vague on what case 
> folding actually _is_ and how it's different from toLower().
> 
> Can someone please tell me the difference and why toCaseFolded() exists in 
> the 
> first place? Is it faster? Is it guaranteed to not make the string 
> longer/shorter?

Maybe http://www.w3.org/International/wiki/Case_folding helps?

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [QML] Need advice on frontend architecture

[Florian Bruhin]

Hey,

* Ronan Jouchet  [2015-11-18 10:46:06 -0500]:
> I recently joined a nascent QML project with the objective to bring it from
> the "working prototype" stage to something maintainable and efficient.
> 
> [...]

This list is for development *of* Qt itself, not *with* it. You
probably want to post this to the Interest mailinglist instead:

http://lists.qt-project.org/mailman/listinfo/interest

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

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

[Florian Bruhin]

* André Somers  [2015-11-05 13:10:33 +0100]:
> Op 5-11-2015 om 00:06 schreef Kevin Kofler:
> >Welbourne Edward wrote:
> >>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 other end there's
> >>a duplicated hour (where 2:59 is followed by a reprise of 2:00 in
> >>Europe, or 1:59 by 1:00 in the USA, IIUC).  While we still need to work
> >>out what behaviour *we* want to give, implementing it is going to depend
> >>on knowing what the platform mktime gives us to work with.
> >The EU actually defines the switchover time in UTC, so which hour is
> >duplicated depends on the actual time zone. It's the 3:mm hour in CET/CEST.
> >
> Nonsense*. I live in the CET (Netherlands), I am 100% sure that the hour
> duplicated is the 2:mm range, not the 3:mm range. At 03:00, the time is
> reset to 02:00 entering winter time again. That happened last October 25.
> Going to summer time, the hour skipped is the 2:mm range also.

While not in the EU, I can confirm what André said for Switzerland as
well :)

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] P1 statistics

[Florian Bruhin]

* Çağdaş Kayra Akman  [2015-10-21 00:42:49 +0300]:
> After being bitten by some showstopper bugs in the last few Qt releases, I
> have decided to gather some P1 statistics. I thought you might find the
> numbers interesting.

Are you aware of the reports JIRA can generate[1]? Might make this
kind of thing easier ;)

Florian

[1] 
https://bugreports.qt.io/browse/QTBUG/?selectedTab=com.atlassian.jira.jira-projects-plugin:reports-panel

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Enhancement to QIODevice?

[Florian Bruhin]

* Andrzej Ostruszka  [2015-09-14 12:25:20 +0200]:
>  From now on I'll talk about QIODevice only since QSerialPort is 
> inheriting from it for the bulk of functionality (and this could also 
> benefit QIODevice).
> 
> Since '\n' is just hardcoded in QIODevice (actually in buffer used in 
> its private part) one option would be to add it as last optional 
> parameter to canReadLine() and readLine() with default value '\n'. What 
> do you think?

As an electronics engineer using Qt, this would definitely make my
life easier sometimes.

I don't think this is about "protocols using weird line-endings" -
it's about the fact there are many sensible choices for low-level
protocols to signal frames, not only \n. As an example, I was dealing
with a protocol (via QSerialPort) which uses STX (start of text,
ASCII 0x02) as delimiter.

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgpGaGeEpB6Fq.pgp
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QString behavior change

[Florian Bruhin]

* Kobus Jaroslaw  [2015-07-31 07:46:07 +]:
> If you say not to differentiate empty and null states, some questions arise:
> 1) Why we have isNull and isEmpty at the same time?
> 2) Why their implementations are different?
> 3) What would be the advice on what to use in general: isNull of isEmpty?

See the documentation of QString::isNull():

Qt makes a distinction between null strings and empty strings for
historical reasons. For most applications, what matters is whether
or not a string contains any data, and this can be determined
using the isEmpty() function.

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgpj9g2oX4dOl.pgp
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] date/time adjust for (auto) testing

[Florian Bruhin]

* André Somers  [2015-06-03 08:38:48 +0200]:
> We have applications that use the current date and time at places spread 
> around the code. For normal operations, that works very nicely. However, 
> we find that for (auto) testing, it would be very convenient if we could 
> trick the application into believing it is some other date/time, so that 
> we can test if certain behaviours work the way we would like to 
> automatically. Currently, these tests take a lot of time because we 
> actually need to manually adjust the system date and time, do some 
> stuff, then adjust again, etc.
> 
> It would be really confortable if there was some control to set a 
> date/time offset (so the time keeps running) or a fixed date/time to be 
> returned from currentDate(), currentTime() or currentDateTime() 
> respectively. I guess access to such a thing does not belong in the main 
> Qt classes, but is really a testing tool, so perhaps it could find 
> refuge in QtTest somewhere. Would a contribution adding such a thing 
> stand any chance of being accepted, or would this be considered out of 
> scope or even unwanted?

FWIW there's libfaketime[1] which might be some inspiration - but
that's Linux/OS X only.

[1] https://github.com/wolfcw/libfaketime

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgpT7qUNSlx4m.pgp
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.4.2 "RC" packages available for your testing

[Florian Bruhin]

* Roland Winklmeier  [2015-05-18 15:24:02 +0200]:
> Hi All,
> 
> I was trying to install the Qt 5.4.2 mingw491 RC package
> (qt-opensource-windows-x86-mingw491_opengl-5.4.2_2015-05-04_23-23-12-132.exe)
> but the installation failed. See attached screenshot (Unfortunately its
> German Language - I didn't find a quick way to change to English).
> I have tried several install options, all with the same result. Does
> anybody else have the same problem? All other installers (5.4.1, 5.5.0
> beta) are fine.

(roughly) translated:

Error while installing component qt.tools.win32_mingw491:
Execution failed (unexpected error code -1073741515): [...]

It looks similiar to this bug, except for 5.4.2 instead of 5.3.0:

https://bugreports.qt.io/browse/QTBUG-38281

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgpnaUskn2aLZ.pgp
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] HEADS-UP: Qt 5.4.2 release coming

[Florian Bruhin]

Hi René,

* René J.V. Bertin  [2015-04-21 21:19:43 +0200]:
> On Tuesday April 21 2015 10:07:49 Thiago Macieira wrote:
> 
> > Either they've been putting up with it or they've never noticed. Either 
> > way, 
> > that makes the bug not critical for a patch release.
> 
> Possibly.
> 
> I've just tried to create a code review for the Qt 4.8 version of my patch. 
> Damn system refused to let me push anything where before I've been able to do 
> so.
> Too bad. The patch will be available through github for anyone who finds this 
> critical enough to (re)build Qt for it.

I'm sure enough people here will be more than happy to help you with
that, but it'd be useful to know what exactly went wrong.

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgpm10wV5MbFJ.pgp
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Deprecating modules with 5.5

[Florian Bruhin]

* Knoll Lars  [2015-03-18 07:31:00 +]:
> On 18/03/15 07:44, "Bo Thorsen"  wrote:
> 
> >Den 17-03-2015 kl. 23:45 skrev Thiago Macieira:
> >> On Tuesday 17 March 2015 17:14:38 Jan Kundrát wrote:
> >>> On Tuesday, 3 February 2015 08:33:46 CET, Knoll Lars wrote:
>  * Qt WebKit
> [...]
> >>>
> >>> You're of course free to do whatever you want to do -- it's just that
> >>>the
> >>> project has promised that this won't happen.
> >> We promised not to break source or binary compatibility. Where are we
> >>doing
> >> that?
> >
> >Removing classes is as binary incompatible as you can possibly make it.
> 
> Deprecating an API is different from removing it. Deprecating is about
> asking people not to use this for new code/projects anymore.

I think that's the point Bo is trying to make - deprecating is fine
(though I'm unhappy with it as QtWebEngine doesn't exactly feel ready
yet), but removing it in 5.6 (as suggested in your original mail)
probably is not.

But if I understood correctly, the consensus here seems to be to
deprecate it in Qt 5.5 and remove it with Qt 6, which sounds much more
reasonable to me.

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgppuOL_At8r9.pgp
Description: PGP signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development