Re: [Development] Qt for WebAssembly status update

Nice overview, thanks Morten! Tor Arne On 6 Jun 2024, at 13:20, Morten Sørvig via Development wrote: Hello all, It’s been a while since the previous update so I figured it was time for a small “state of the union” on the WebAssembly port. I’ll focus on topics which are most relevant to

Re: [Development] Nominating Tim Blechmann for approver

+1!!! > On 22 May 2024, at 10:52, Jøger Hansegård via Development > wrote: > > Hi all, > > I would like to nominate Tim Blechmann for approver rights in the Qt project. > > Since 2013, Tim has been an active contributor to Qt, providing strong > patches and insightful reviews. Currently, he

Re: [Development] Moving QDesktopServices from Gui to Core?

> On 8 May 2024, at 07:32, Marc Mutz via Development > wrote: > > I'd like an option that actually solves for the needs of QtNetworkAuth. 1. Move the plumbing of the URL handling to private APIs in QtCore, used by QDesktopServices 2a. Add a helper

Re: [Development] Moving QDesktopServices from Gui to Core?

> On 7 May 2024, at 12:51, Marc Mutz via Development > wrote: > > On 06.05.24 13:08, Tor Arne Vestbø via Development wrote: >> >> >>> On 6 May 2024, at 13:06, Juha Vuolle wrote: >>> >>>> QtNetworkauth leaves the QDesktopServices::o

Re: [Development] Moving QDesktopServices from Gui to Core?

> On 6 May 2024, at 13:06, Juha Vuolle wrote: > >> QtNetworkauth leaves the QDesktopServices::openUrl() usage/non-usage >> at the user's discretion, and thus that currently won't force a Gui >> dependency. > > (Ah shoot. Correcting myself, in the new qtnetworkauth class we do > need to call

Re: [Development] Moving QDesktopServices from Gui to Core?

> On 6 May 2024, at 12:31, Allan Sandfeld Jensen wrote: > > On Monday 6 May 2024 10:02:43 CEST Tor Arne Vestbø via Development wrote: >> There’s some overlap here with the more modern features of intents, >> activities, etc, which we are hoping to add proper APIs for a

Re: [Development] Moving QDesktopServices from Gui to Core?

There’s some overlap here with the more modern features of intents, activities, etc, which we are hoping to add proper APIs for at some point, so I suggest not doing any public API changes as part of this. We can move the registration APIs to QtCore as private APIs, that QtNetworkAuth can use,

Re: [Development] RFC: New keyword for Fixes bot "Reopens" and revert detection

On 15 Apr 2024, at 12:07, Daniel Smith via Development wrote: I'd like to open up a thread for discussion on the addition of a new commit message footer, "Reopens", related to Fixes/Task-Number. The proposed behaviour is: * Use of "Reopens: QTBUG1234" would trigger automatic reopening of

[Development] Nominating Jøger Hansegård for approver rights

Hi, I would like to nominate Jøger Hansegård for approver rights in the Qt project. Jøger joined The Qt Company 10 months ago and has since then been getting his hands dirty in Qt Multimedia, and lately focusing on color management. Jøger is a thorough and responsible engineer and I trust that

Re: [Development] Nominating Dr. Máté Barany as an approver for the Qt project

+1! On 6 Mar 2024, at 23:09, Axel Spoerl via Development wrote: Dear Colleagues, I hereby nominate Dr. Máté Barany as an approver for the Qt project. Máté has been a valuable contributor and reviewer, providing sound code, guidance and input. As a reference, see his dashboard

Re: [Development] Using '#pragma once' instead of include guards?

The choice of where we use/allow `#pragma once` should not be coupled to whether a header is considered public or not. Let’s not create even more indirections and inference rules that one has to keep in mind. If we want to make it clearer if a header is public or not, let’s make it explicit.

Re: [Development] Nominating Piotr Wierciński for approval status

+1 :) > On 8 Feb 2024, at 09:39, Morten Sørvig via Development > wrote: > > I would like to nominate Piotr Wierciński for approver rights in the Qt > project. > > Piotr joined the Qt company early 2013 and has since then contributed to Qt > for WebAssembly. This includes many bugfixes and

Re: [Development] Nominating Vlad Zahorodnii for approval status

+1! > On 1 Feb 2024, at 15:11, David Edmundson wrote: > > I would like to nominate Vlad Zahorodnii for approver rights in the Qt > project. > > Vlad has also been working on the QtWayland backend, providing insight > based on his other role as one of the kwin maintainers. > Vlad and I have

Re: [Development] Nominating David Redondo for approval status

+1! > On 1 Feb 2024, at 15:10, David Edmundson wrote: > > I would like to nominate David Redondo for approver rights in the Qt project. > > David's first contributions to Qt started in November 2020, but has > ramped up this last year working on the Qt Wayland platform. Not only > has he fixed

Re: [Development] Nominating Matthias Rauter for approval status

+1! On 30 Jan 2024, at 13:11, Paul Tvete via Development wrote: Hi, I would like to nominate Matthias Rauter as an approver for the Qt Project. Matthias has been working on Qt for more than a year now. In this time, he has done great work on Qt Location and Qt SVG, among other. I have had

Re: [Development] Stepping down as Android maintainer

Thanks for all your work BogDan! And a strong +1 to Assam! Tor Arne 8. jan. 2024 kl. 09:47 skrev BogDan Vatra via Development : Hello there, I have been less active on the Android port recently and Assam has been doing the majority of the work maintaining the Android port. I'm therefor

Re: [Development] QML Rectangle corner radius API for Qt 6.7

On 22 Dec 2023, at 13:59, André Somers wrote: And what type would the radius property return then? I guess it would have to be the grouped type. But that would break all code that currently creates a binding on radius expecting it to be a real. True, that would not work too well. The

Re: [Development] QML Rectangle corner radius API for Qt 6.7

On 22 Dec 2023, at 13:59, Lars Knoll wrote: You don't often get email from l...@knoll.priv.no<mailto:l...@knoll.priv.no>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> On 22 Dec 2023, at 13:54, Tor Arne Vestbø via Development wrote: On 22 Dec 20

Re: [Development] QML Rectangle corner radius API for Qt 6.7

On 22 Dec 2023, at 13:54, Tor Arne Vestbø wrote: We can change the `radius` property from a qreal into a group property with left/rigth/top/bottom, similar to anchors. We can detect in the setRadius setter if the incoming argument is a real, and apply that to all of the corners. That would

Re: [Development] QML Rectangle corner radius API for Qt 6.7

> On 22 Dec 2023, at 13:20, Giuseppe D'Angelo via Development > wrote: > > Il 22/12/23 11:15, André Somers ha scritto: >> I can see two options. The simplest option is to have a `radii` >> property, which is a grouped property containing the `topLeft`, >> `topRight`, `bottomLeft` and

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

leftovers. There are developers/customers using it in their production environment already, also outside of the automotive sector. BR, Maurice From: Development On Behalf Of Tor Arne Vestbø via Development Sent: Thursday, 7 December 2023 18:37 To: Tuukka Turunen Cc: Macieira, Thiago ; development@qt-project.o

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

If it’s an option to rename this module we should take the opportunity to do so I think. The problem of the generic naming came up in the past, but the understanding was that it was too late to change. If that is not the case after all, we should strongly consider it. The documentation at

Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)

The naming makes sense, given their purpose. But can we put them in a dedicated Qt::std_compat namespace? Or is that too late? That would make it clear these are not Qt proper types (living in the Qt namespace), but dedicated compat types/BC/SC vehicles . Tor Arne On 14 Nov 2023, at 10:00,

Re: [Development] Failed to run configure.bat in qt/qt5 repository on Windows?

If the goal here is to build documentation, I recommend installing Qt from the installer, and then doing a local build with e.g.: cd ~/build/qt/6.x-doc && ~/dev/qt/configure -developer-build -nomake examples -nomake tests -no-warnings-are-errors -submodules qtbase,qtdoc -qt-host-path

Re: [Development] Changes to automatic cherry-picking

Thanks Daniel! This sounds like a better model with less chance of orphaned changes. > On 24 Jul 2023, at 10:07, Daniel Smith via Development > wrote: > […] > Because this change takes away some level of control from the user, a new > footer is being introduced. A new footer, proposed as

Re: [Development] API style guide: scoped enum or not?

> On 14 Jun 2023, at 17:48, Thiago Macieira wrote: > > On Wednesday, 14 June 2023 08:35:16 PDT Marc Mutz via Development wrote: > B) new enums MUST be scoped, also when nested in classes¹² -1 Disagree >>> >>> -1 Disagree >> >> Ok. But _why_? (Q to both) > > I'm inclined to

Re: [Development] API style guide: scoped enum or not?

On 14 Jun 2023, at 16:20, Allan Sandfeld Jensen wrote: On Mittwoch, 14. Juni 2023 14:59:40 CEST Marc Mutz via Development wrote: On 02.05.23 10:58, Volker Hilsheimer via Development wrote: During the header review, but also in API discussions leading up to it, we had a few cases where it would

[Development] Bumping the minimum CMake version for Apple platforms to 3.21 for Qt 6.6

Hi all, We currently require CMake 3.16 for shared builds, and 3.21 for static builds. CMake 3.16 unfortunately doesn't have a feature we rely on on Apple platforms — finalizers — requiring us to maintain and take into account additional APIs for users to manually finalize their projects, with

Re: [Development] Nominating Artem Dyomin as Approver

+1! (Disclaimer: Artem reports to me directly). On 27 May 2023, at 18:02, Volker Hilsheimer via Development wrote: +1, he’s doing great. Disclaimer: Artem sits across the hall from me in the office, works down the street from me in home office, and reports to me indirectly. Volker

Re: [Development] Nominating Edward Welbourne as QLocale / date/time maintainer

+1! > On 4 May 2023, at 12:10, Marc Mutz via Development > wrote: > > Hi, > > I'd like to nominate Eddy as the maintainer for the QLocale and > src/corelib/time QtCore subsystems. Eddy is filling that role de-facto > already; making it de-jure sounds only logical. > > I asked, and he'd be

Re: [Development] API style guide: scoped enum or not?

On 3 May 2023, at 19:22, Thiago Macieira wrote: I'd say that any new enumeration in the Qt namespace should be enum class, but enums in classes may not be so if they're sufficiently descriptive already. Agreed, and this is also what our current API design guide says:

Re: [Development] API style guide: scoped enum or not?

On 3 May 2023, at 18:40, Giuseppe D'Angelo via Development wrote: Il 02/05/23 10:58, Volker Hilsheimer via Development ha scritto: During the header review, but also in API discussions leading up to it, we had a few cases where it would have helped if we had clearer guidelines about when to

[Development] Archiving of the '6.x' version in JIRA

Hey all, We’re planning on archiving the '6.x’ version in JIRA: https://bugreports.qt.io/projects/QTBUG/versions/18732 Now that Qt 6 has been out for a while, the version

Re: [Development] Qt Multimedia: proposing behavior change to QAudioSink::resume

Hi, This does indeed look like an oversight, where the behavior was perhaps modeled under the assumption the buffers were empty at the time of suspend(). I would expect the state to return back to the same state the sink had when calling suspend(). Cheers, Tor Arne > On 30 Jan 2023, at

Re: [Development] New Qt example development guideline and revamping examples

On 20 Jan 2023, at 09:49, Eike Ziller wrote: Am 19/01/2023 um 13:33 schrieb Giuseppe D'Angelo via Development : Il 19/01/23 10:27, Tor Arne Vestbø ha scritto: All the contrary, do NOT do that, as it results in 200+ lines unnamed lambdas. Strongly prefer named slots. Keep the lambdas short

Re: [Development] New Qt example development guideline and revamping examples

> On 18 Jan 2023, at 13:12, Giuseppe D'Angelo via Development > wrote: > >> RECOMMENDED >>Prefer signal/slot connection with lambdas: >> https://doc.qt.io/qt-6/signalsandslots.html > > All the contrary, do NOT do that, as it results in 200+ lines unnamed > lambdas. Strongly prefer

Re: [Development] Nominating Mikołaj Boć as approver

+1! (I’m Mikołaj’s direct manager) On 21 Dec 2022, at 15:21, Morten Sørvig via Development wrote: Hi, I’d like to nominate Mikołaj Boć as an approver for the Qt project. Mikołaj joined the Qt Company earlier this year and hit the ground running. He has contributed features and many bug

Re: [Development] Nominating Axel Spoerl as approver

+1 Very impressed with his fearless adventures into the abyss of flakey tests! Cheers, Tor Arne > On 5 Dec 2022, at 10:57, Volker Hilsheimer via Development > wrote: > > Hi, > > > I’d like to nominate Axel Spoerl as an approver for the Qt project. > > Axel has been working in The Qt

Re: [Development] Nominating Mårten Nordheim and Timur Pocheptsov as new co-maintainers of Qt WebSocket

+1 > On 29 Nov 2022, at 14:55, Volker Hilsheimer via Development > wrote: > > Hi, > > > Kurt Pattyn is currently listed as the Maintainer fo Qt WebSocket. However, > he has not responded to emails I sent him over the last few months. In the > middle of October I informed him that I will

Re: [Development] I ❤️ Qt containers! :) (was: How qAsConst and qExchange lead to qNN)

> On 8 Nov 2022, at 14:25, Volker Hilsheimer via Development > wrote:  Tor Arne ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Adding CPD support to Qt print dialog

That’s awesome, nice work Gaurav! - Tor Arne On 26 Sep 2022, at 18:47, Gaurav Guleria wrote:  Yes, CPDB is just a different backend for the existing print dialog GUI. It's merely a different way of enumerating printers and their features. I have already prepared a simple CPDB plugin (still

Re: [Development] Adding CPD support to Qt print dialog

> On 26 Sep 2022, at 17:19, Till Kamppeter wrote: > > But we must also take into account that Gaurav has not arbitrarily much time. > His GSoC project is already in the extension. So he needs to know now how he > can get CPDB support in quickly, especially without need to design a new GUI >

Re: [Development] Adding CPD support to Qt print dialog

On 26 Sep 2022, at 16:54, Volker Hilsheimer mailto:volker.hilshei...@qt.io>> wrote: On 25 Sep 2022, at 20:58, Albert Astals Cid mailto:aa...@kde.org>> wrote: El dissabte, 24 de setembre de 2022, a les 12:45:00 (CEST), Tor Arne Vestbø va escriure: On 23 Sep 2022, at 19:21+0

Re: [Development] Adding CPD support to Qt print dialog

CPDB print backend up. Once we get to that point we can look at possibly adding new API for the print engines to deal with the needs of QCupsJobWidget and the like, so that we don’t need CUPS/CPDB specifics in the dialog code. Cheers, Tor Arne > > On 9/19/22 21:59, Tor Arne Vestbø wrot

Re: [Development] Adding CPD support to Qt print dialog

> On 19 Sep 2022, at 18:21, Till Kamppeter wrote: > > On 19/09/2022 15:43, Tor Arne Vestbø wrote: >>> >>> First is to create a new Qt print backend, what, instead of communicating >>> directly with CUPS, communicates with the CPDB backends. It is some k

Re: [Development] Adding CPD support to Qt print dialog

> On 19 Sep 2022, at 00:51, Till Kamppeter wrote: > We do not do any GUI design or change as part of our project. We only add a > new method to obtain the available printers, their capabilities and options, > and to send off print jobs to them. That’s good news. > > First is to create a

Re: [Development] Nominating David and Eskil as Qt Wayland maintainers

+1 ! Cheers, Tor Arne > On 24 Aug 2022, at 10:36+02:00, Volker Hilsheimer > wrote: > > Hi, > > > Giulio has informed me that he won’t be able to continue as the maintainer of > Qt Wayland. Thanks Giulio for your contribution! > > Qt Wayland is currently listed as a single module on the

Re: [Development] Windows plugin customisation: QWindowsKeyMapper

o pass through the app AFAICT. Tor Arne On Sat, Jul 30, 2022 at 5:15 PM Tor Arne Vestbø mailto:tor.arne.ves...@qt.io>> wrote: Actually, you might be able to filter out the event via https://doc.qt.io/qt-6/qcoreapplication.html#installNativeEventFilter And pass it on manually to

Re: [Development] Windows plugin customisation: QWindowsKeyMapper

Actually, you might be able to filter out the event via https://doc.qt.io/qt-6/qcoreapplication.html#installNativeEventFilter And pass it on manually to windows via DefWindowProc Tor Arne On 30 Jul 2022, at 18:12, Tor Arne Vestbø mailto:tor.arne.ves...@qt.io>> wrote: Hi, I don’t

Re: [Development] Windows plugin customisation: QWindowsKeyMapper

Hi, I don’t think there’s any way to customize that behavior today, apart from maintaining a customized version of the Windows platform plugin. You could perhaps have some luck intercepting WM_APPCOMMAND before it reaches the Qt message proc? Tor Arne On 30 Jul 2022, at 14:12, Laszlo Papp

[Development] Feature freeze exception for permission API

Hi, The permission API (https://bugreports.qt.io/browse/QTBUG-90498 / https://codereview.qt-project.org/c/qt/qtbase/+/409324) was planned for Qt 6.4, but unfortunately did not stabilize enough in time for the freeze. To avoid pushing the API to 6.5, and to get some user feedback on the both

Re: [Development] Using Git notes to reflect actual cherry-picks

See comment in review. I think a prerequisite for running this kind of script against our repos is that the notes are namespaced, e.g. refs/notes/cherry-picks so that fetching and showing them in git log output is optional. Other than that I think it’s a nice feature :) Tor Arne On 25 May

Re: [Development] Jira tickets for Qt Print Support (Was: Volunteer wanted: update use of CUPS API)

On 5 May 2022, at 10:32, Alex Blasche mailto:alexander.blas...@qt.io>> wrote: -Original Message- From: Development mailto:development-boun...@qt-project.org>> On Behalf Of Sze Howe Koh On Mon, 4 May 2020 at 15:19, Lars Knoll mailto:lars.kn...@qt.io>> wrote: On 4 May 2020, at 09:08,

Re: [Development] Nominating David Skoland as approver

+1! Disclaimer: I am David's line manager in The Qt Company. Cheers, Tor Arne On 21 Apr 2022, at 14:00, Morten Sørvig mailto:morten.sor...@qt.io>> wrote: I'd like to nominate David Skoland as approver for the Qt Project. David is employed by the Qt company has been contributing to Qt since

Re: [Development] Nominating Morten Sørvig as maintainer of high-DPI

This has now been effectuated: https://wiki.qt.io/Maintainers#Qt_Maintainers Cheers, Tor Arne On 4 Jan 2022, at 16:18, Eirik Aavitsland mailto:eirik.aavitsl...@qt.io>> wrote: +1! - Eirik Aa. On 12/20/21 4:35 PM, Tor Arne Vestbø wrote: Hello all, I’d like to nominate Morten

Re: [Development] Using Git notes to reflect actual cherry-picks

Very cool! As ossi suggests, this could potentially be handled by Gerrit, similar to this:

Re: [Development] XCB platform plugin maintainer change

ms/xcb$ git shortlog --since=2021 --no-merges -s -n . 11 Liang Qi 6 Tor Arne Vestbø 3 Gatis Paeglis I would like to propose Liang Qi as the new maintainer. He has been with the company for more than a decade. Gatis Paeglis. ___ Devel

Re: [Development] Proposing to officially allow C++20 types in Qt 6 ABIs

> On 27 Jan 2022, at 18:14, Thiago Macieira wrote: > > On Thursday, 27 January 2022 08:53:31 PST Tor Arne Vestbø wrote: >> I don’t know what other things you’re referring to, but just to clarify, >> this is not the case for macOS. We build the binary Qt packages with as

Re: [Development] Proposing to officially allow C++20 types in Qt 6 ABIs

> On 27 Jan 2022, at 17:19, Thiago Macieira wrote: > > We know a great deal of our users use the binary builds by the Qt Company. In > order to make those the most widely supported, they are compiled with the > oldest compiler we still support. I don’t know what other things you’re

Re: [Development] Nominating Volker Hilsheimer as co-maintainer of Qt Widgets

+1! > On 25 Jan 2022, at 09:38, Richard Gustavsen wrote: > > Hi all! > > I would like to propose a change in the maintenance of Qt Widgets [1]. I’m > the current maintainer of the module, but I’m happy to inform you that Volker > Hilsheimer has agreed to join me as a co-maintainer. Volker is

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

+1! > On 19 Jan 2022, at 12:59, Volker Hilsheimer wrote: > > Hi, > > I’d like to nominate Dimitrios Apostolou, aka Jimis, as approver in the Qt > Project. > > Jimis has been working as a Software Engineer in the Qt Company since 2019 > and has made a number of contributions [0] and reviews

Re: [Development] Updating x86 SIMD support in Qt

Hey hey, On 19 Jan 2022, at 04:01, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: 3) add a way to have multi-arch glibc-based Linux builds If we go down this road I ask that we align both the porcelain and plumbing (configure, build system, C++ APIs, etc) . We already have

[Development] Nominating Morten Sørvig as maintainer of high-DPI

Hello all, I’d like to nominate Morten Sørvig as maintainer of high-DPI in the Qt Project [1]. Morten has been instrumental in the development of Qt’s high-DPI support, and has been the de-factor maintainer for a while now. Let’s make it official. Cheers, Tor Arne [1] Under qtbase/QtGui in

Re: [Development] Qt 6 not seeing the same DPI as Qt 5

On 29 Nov 2021, at 23:43, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On Monday, 29 November 2021 13:20:58 PST Tor Arne Vestbø wrote: If you know that the physical DPI being reported is correct you can use QT_USE_PHYSICAL_DPI to override the behavior as documented.

Re: [Development] Qt 6 not seeing the same DPI as Qt 5

On 29 Nov 2021, at 19:05, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On Monday, 29 November 2021 09:09:16 PST Tor Arne Vestbø wrote: What's changed between 5 and 6? https://doc-snapshots.qt.io/qt6-dev/highdpi.html#configuring-x11 Thanks, Tor Arne. I see in th

Re: [Development] Qt 6 not seeing the same DPI as Qt 5

Cheers, Tor Arne On 29 Nov 2021, at 17:41, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: I'll probably have to report this as a bug, but just in case someone has seen it before: $ diff -u qtdiag5 qtdiag6 [...] Geometry: 1920x1200+0+0 (native: 3840x2400+0+0) Available:

Re: [Development] Proposing to move deploy tools to qtbase

Agreed, +1 Cheers, Tor Arne On 16 Nov 2021, at 15:23, Ulf Hermann mailto:ulf.herm...@qt.io>> wrote: I’m working on adding new CMake APIs for install support for Qt 6.3. As part of that, there will be conveniences for invoking the appropriate xxxdeployqt tool where available. At the moment,

Re: [Development] Jira and issues left "In Progress"

On 1 Nov 2021, at 12:27, David Skoland mailto:david.skol...@qt.io>> wrote: One caveat: Jira has no state for indicating "the work is done but not yet integrated" This is a good point. We could add a state in Jira called something like “Patch submitted” in the In Progress status category.

Re: [Development] Nominating Oliver Eftevaag as Approver

+1 On 27 Oct 2021, at 06:25, Paul Wicking mailto:paul.wick...@qt.io>> wrote: Hi all, I'd like to nominate Oliver Eftevaag as an approver. Oliver has been working as a software engineer for the Qt Company for almost a year now and has made a fair number of contributions to Qt [0]. He also

Re: [Development] Nominating Doris Verria as Approver

+1 > On 27 Oct 2021, at 11:56, Volker Hilsheimer wrote: > > Hello World, > > I’d like to nominate Doris Verria as approver in the Qt Project. > > Doris has been working as a Software Engineer for The Qt Company for over a > year, and has made great contributions to Qt [0]. I have come to

Re: [Development] Qt Android Extras "stopgap"

On 18 Sep 2021, at 11:43, Jarkko Koivikko mailto:jarkko.koivi...@code-q.fi>> wrote: The correct header is: #include Thanks, updated blog post, docs will follow. Cheers, Tor Arne ___ Development mailing list Development@qt-project.org

Re: [Development] Feature freeze exception for QTBUG-95587

I agree, this feels like it should have some wider discussion. Cheers, tor arne > On 13 Sep 2021, at 13:27, André Somers wrote: > > > On 09-09-2021 17:32, Ulf Hermann wrote: >> Hello, >> >> due to the magnitude of the above mentioned bug, I'm considerng to introduce >> a new feature in Qt

Re: [Development] Merging qtquickcontrols2 into qtdeclarative

On 12 Jul 2021, at 21:19, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: So a full history import MAY have negligible marginal impact over a squashed import (.git is compressed). I recommend trying both and seeing by how much the qtdeclarative repository increases, then deciding

Re: [Development] Merging qtquickcontrols2 into qtdeclarative

On 12 Jul 2021, at 17:03, Oswald Buddenhagen mailto:oswald.buddenha...@gmx.de>> wrote: On Mon, Jul 12, 2021 at 02:17:01PM +0000, Tor Arne Vestbø wrote: One way to do this is with a prefixed subtree merge without squashing the history of controls2. What ossi (?) referred to was usi

Re: [Development] Merging qtquickcontrols2 into qtdeclarative

One way to do this is with a prefixed subtree merge without squashing the history of controls2. What ossi (?) referred to was using git replace to inject the history of controls, but I’m not sure how that would look so perhaps he can outline that approach. Cheers, Tor Arne On 12 Jul 2021, at

Re: [Development] Version-controlling the SVGs of built-in icons

Hey hey, Thanks for bringing this up, I’ve been in that situation myself, for example looking for diagrams in the documentation. I generally think that assets that make up a product should live together. That is, the source code, image assets, docs, examples, tests, etc, for a

Re: [Development] Windows maintainer change

Hear hear! +1 > On 15 Jun 2021, at 11:05, Shawn Rutledge wrote: > > +1 > > Thanks for the work that all 3 of you have put into it over the years. > >> On 15 Jun 2021, at 09:27, Oliver Wolff wrote: >> >> Hi all, >> >> I would like to propose a change in Qt's Windows maintainership. I think

Re: [Development] New Qt Multimedia

Cheers, Tor Arne On 28 May 2021, at 10:54, Samuel Gaist via Development mailto:development@qt-project.org>> wrote: On 28 May 2021, at 10:37, Lars Knoll mailto:lars.kn...@qt.io>> wrote: How have you implemented those? If you implemented a gstreamer element for those cameras, and

Re: [Development] Mac Big Sur - Qt Open-Source Support For

ons beyond the > very narrow scope of this question.  Cheers, Tor Arne > > Kind regards, > Robert Iakobashvili > > > On Fri, May 7, 2021 at 12:47 PM Tor Arne Vestbø wrote: >> >> Qt 6.0 and above has official support for Big Su

Re: [Development] Mac Big Sur - Qt Open-Source Support For

Qt 6.0 and above has official support for Big Sur: https://doc.qt.io/archives/qt-6.0/macos.html 5.15 is not yet officially supported, but should work fine as well, so please report any issues in JIRA, thanks! Cheers, Tor Arne On 7 May 2021, at 11:00, coroberti mailto:corobe...@gmail.com>>

Re: [Development] New features in CI

On 1 Mar 2021, at 17:22, Edward Welbourne mailto:edward.welbou...@qt.io>> wrote: If a staging branch passes, all the changes contained in that branch will be merged into the target branch (can be a fast-forward merge). you mean actual git merges, rather than rebases/cherry-picks? that will

Re: [Development] User-defined literals for QString (and QByteArray)

On 3 Mar 2021, at 16:53, Andrei Golubev mailto:andrei.golu...@qt.io>> wrote: QString hello = u"Hello"; // oops, compilation error This seems like a bug though? From an API point of view, I’d expect this simple assignment to JustWorkTM, without requiring syntactic sugar all over the place.

Re: [Development] Qt 6 co-installability with Qt 5

> On 17 Feb 2021, at 23:39, Thiago Macieira wrote: > > On Wednesday, 17 February 2021 00:32:13 PST Joerg Bornemann wrote: >> Yes, and that's all good, and with >> https://codereview.qt-project.org/c/qt/qtbase/+/334054 we will have an >> offical recommendation. >> I will also add a documentation

Re: [Development] Qt 6 co-installability with Qt 5

> On 16 Feb 2021, at 14:31, Kai Köhne wrote: > > Well, let's just realize that, by renaming qmake to qmake6 everywhere > (including in the documentation), we actually create some confusion for our > existing users, too. Also, I think adding version numbers to the name of > tools is just no

Re: [Development] Qt modules, API changes and Qt 6

On Tue, Sep 17, 2019 at 12:39:01PM +, Simon Hausmann wrote: Am 17.09.19 um 14:27 schrieb Oswald Buddenhagen: for example, the information that a build with updated dependencies is required can be stored as an annotation in the commit message (that's exactly what zuul does, afaik), and the

Re: [Development] Qt6 repo

Cheers, Tor Arne On 13 Jan 2021, at 14:37, Volker Hilsheimer mailto:volker.hilshei...@qt.io>> wrote: On 13 Jan 2021, at 14:17, Dominik Holland mailto:dominik.holl...@qt.io>> wrote: Am 1/13/21 um 1:19 PM schrieb Allan Sandfeld Jensen: On Mittwoch, 13. Januar 2021 13:07:00 CET NIkolai

Re: [Development] Qt6 repo

> > On 13 Jan 2021, at 12:38, Allan Sandfeld Jensen wrote: > > On Mittwoch, 13. Januar 2021 12:31:50 CET Eric Lemanisser wrote: >> that's the obvious choice, if it was not already used by qt4. >> > Then rename the qt4 repo, it is not actively maintained anymore and only > stored for history.

Re: [Development] Switch the main "Qt Build System"

Awesome work!!  Cheers, Tor Arne On 8 Dec 2020, at 17:51, Alexandru Croitor mailto:alexandru.croi...@qt.io>> wrote: Hi again, A short update on the build system switch. Sine my last email (half a year ago) a number of issues were raised that we had to tackle in order to consider switching

Re: [Development] Qt 6 co-installability with Qt 5

On 18 Nov 2020, at 14:21, Lisandro Damián Nicanor Pérez Meyer mailto:perezme...@gmail.com>> wrote: On Wed, 18 Nov 2020 at 10:16, Tor Arne Vestbø mailto:tor.arne.ves...@qt.io>> wrote: On 18 Nov 2020, at 14:01, Lisandro Damián Nicanor Pérez Meyer mailto:perezme...@gmail.com>&

Re: [Development] Qt 6 co-installability with Qt 5

> On 18 Nov 2020, at 14:01, Lisandro Damián Nicanor Pérez Meyer > wrote: > > On Wed, 18 Nov 2020 at 09:58, Tor Arne Vestbø wrote: > [snip] >> Let’s clarify this, so we’re talking about the same thing: >> >> 1. Application end-users >> 2. Application

Re: [Development] Qt 6 co-installability with Qt 5

On 18 Nov 2020, at 13:39, Lisandro Damián Nicanor Pérez Meyer mailto:perezme...@gmail.com>> wrote: Right, and this are all developer's tools. End users shouldn't care nor even know about them. Remember, we are talking about distribution-provided binaries. Let’s clarify this, so we’re talking

Re: [Development] Qt 6 co-installability with Qt 5

On 18 Nov 2020, at 12:11, Tor Arne Vestbø mailto:tor.arne.ves...@qt.io>> wrote: What we need is a command line tool for doing the same. That’s how other project solve things too (nvm, rvm, pyenv, etc) For some context: * https://github.com/nvm-sh/nvm * https://rvm.io/ *

Re: [Development] Qt 6 co-installability with Qt 5

Morning, IMHO, suffixing our binaries is a kludge. It “solves” the major version transition, but not any of the other use cases such as minor version upgrades, different builds of the same Qt version, etc. Qt Creator already provides a way to manage and switch Qt versions:

Re: [Development] Proposal: let's use Markdown for the dist/changes changelog

> On 3 Nov 2020, at 10:52, Richard Gustavsen wrote: > > Would it be better if we required all commits to have a ChangeLog entry, so > that no one > forgets? And if your commit shouldn't be in the log, you need to state that > explicitly, e.g: [NoChangeLog] No, that would just add noice to

Re: [Development] Qt 6 co-installability with Qt 5

On 27 Oct 2020, at 19:34, Marius Kittler mailto:mkitt...@suse.de>> wrote: For the Windows target that counts as well besides the "qtmain" problem. I used so far the following patch to workaround it: https://github.com/Martchus/PKGBUILDs/commit/

Re: [Development] Is qsizetype *documented* to be ptrdiff_t?

> On 2 Sep 2020, at 16:49, Thiago Macieira wrote: > > Tor Arne wrote: >> As a user of this API I was also stumped by not being able to just call >> printf with %z and a qsizetype, under the assumption that qsizetype’s >> purpose in life was to mask _away_ the differences of what a size was >>

Re: [Development] Is qsizetype *documented* to be ptrdiff_t?

As a user of this API I was also stumped by not being able to just call printf with %z and a qsizetype, under the assumption that qsizetype’s purpose in life was to mask _away_ the differences of what a size was represented as. Since it all flattens down to e.g. qint64 I don’t suppose there’s

Re: [Development] Qt5.14 Prl files are missing for Mac framework build?

> On 27 Jul 2020, at 23:55, Иван Комиссаров wrote: > > Hello again! > > What about qt6? In the snapshot files are back in framework root… Is that a > regression? Yeah, that’s a regression when transitioning to CMake. Thanks for the heads up! Tor Arne

Re: [Development] [RFO QTBUG-84739] QJsonValue::fromVariant containing QByteArray

> On 3 Jul 2020, at 02:49, Thiago Macieira wrote: > > On Thursday, 2 July 2020 15:46:24 PDT Tor Arne Vestbø wrote: >> I think I prefer permanently, and then clearly documenting that the fallback >> conversion to a string for non-listed types may be lossy, teaching the use

Re: [Development] [RFO QTBUG-84739] QJsonValue::fromVariant containing QByteArray

> On 2 Jul 2020, at 19:07, Thiago Macieira wrote: > > On Thursday, 2 July 2020 03:57:08 PDT Tor Arne Vestbø wrote: >> Which does not match the documented behavior, so I think a revert makes >> sense to avoid the surprising behavior change. > > Thanks for the opinio

  1   2   3   >