[Development] Qt Examples need to be self-contained

s for affected examples. Regards Kai PS: To be clear, this is not something we still have to fix for Qt 6.7.0. For now, the use of Junction points in Qt Creator is still opt-in. When we fix examples, we should still backport them to older Qt versions though. -- Kai Köhne, Director R | The Qt Com

Re: [Development] Extending qt_attribution.json files to mark provisioned components

Hi Volker! > From: Volker Hilsheimer > Sent: Tuesday, March 5, 2024 10:40 > To: Kai Köhne > Cc: development@qt-project.org > Subject: Re: [Development] Extending qt_attribution.json files to mark > provisioned components >  > > >> On 4 Mar 2024, at

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

Hi Marc, I've nothing against using '#pragma once' for private/internal headers. But you said you mainly want to have this to differentiate between different types of headers. If this is the motivation, I think we can make this differentiation even more explicit. For instance, public headers

[Development] Extending qt_attribution.json files to mark provisioned components

qtattributionsscanner change: https://codereview.qt-project.org/c/qt/qttools/+/545098 Let me know what you think. Regards Kai -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Str. 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft

Re: [Development] Let's drop MSVC 2019 for dev (6.8)

> MSVC2019 and MSVC2022 is supposed to be compatible. So in theory at least > packages made with MSVC2022 is still usable for MSVC2019 as well. It is just a > question of which compiler we use to generate the binaries with. That's not the case, at least according to Microsoft

Re: [Development] HEADS-UP: Qt 6.7 API change review

Hi, also a reminder from my side: When checking out any API changes, please also check the API _documentation_. A good start for this is https://doc-snapshots.qt.io/qt6-6.7/newclasses67.html New API * Is it documented, and marked with \since? * Is the documentation in good shape (grammar,

Re: [Development] Lots of qdoc-related warning messages when building 'docs' target in Qt-6.6.0?

Hi, QDoc needs to parse C++ sources to actually generate the API documentation. This requires a build where the modules are actually configured. This explains some of the warnings you see - Qt WebEngine, Qt PDF cannot be built on MinGW, and likewise Qt Wayland (Compositor). Anyway, like Paul

[Development] How to document API only deprecated in future Qt versions

with the new API. But it's not something we've done so far, IMO. Do you agree? Kai -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Str. 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht

[Development] Avoid QT_BEGIN_NAMESPACE..QT_END_NAMESPACE in Qt examples

are rather small, the benefits of this optimization are neglectable. Happy to hear any feedback, either here or, preferably, in the Gerrit commit. Kai [1]: https://contribute.qt-project.org/quips/13 -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Str. 10, D-12489 Berlin

[Development] Documenting API changes in Qt Framework

version it applies to. Thanks for your consideration! Regards Kai -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Str. 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht

Re: [Development] On the use of the inline keyword

Not an GCC expert, but this is the code that emits the warning in GCC: https://github.com/gcc-mirror/gcc/blob/66be6ed81f369573824f1a8f5a3538a63472292f/gcc/attribs.cc#L1818 First argument for warning() is 0 ... which explains why it cannot be easily disabled with say -Wno-ignored-attributes. I

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

> The question you must answer is why git > submodule update isn't checking those > commits out for those submodules. > > Anyway, why are you checking out 6.2.4 using Git? That's the key: qtlocation and qtspeech weren't part of 6.2 qt5.git. So when switching from dev to 6.2.4, 'git checkout'

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

> I followed what you said, build qminimal manually. > However, after that, it still failed to build docs target. Like I said in a previous mail, you need qminimal and qsqlite (at least if you don't use latest dev). So make this: cmake --build . --parallel 4 --target qminimal qsqlite cmake

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

> so running > $ ninja qdoc qtattributionsscanner > qhelpgenerator. > should hopefully be sufficient Actually both are dependencies of the doc target. And since https://codereview.qt-project.org/c/qt/qttools/+/494893, just running configure cmake --build . docs should be enough. If you're

Re: [Development] [RFCs] Migrate from GCC MinGW to LLVM MinGW

> From: Development on behalf of Yang Fan > > Sent: Thursday, July 20, 2023 3:55 AM > To: Cristian Adam > Cc: development@qt-project.org > Subject: Re: [Development] [RFCs] Migrate from GCC MinGW to LLVM MinGW > > I wanted to point out that MSYS2 offers precompiled packages of Qt6 in > four

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

> -Original Message- > From: Development On Behalf Of > Hasselmann Mathias via Development > Subject: Re: [Development] Support for *Notes and UpstreamFiles fields in > qt_attributions.json files > > Hi, > > Just to make ensure all options are considered: How about the elephant in the >

Re: [Development] Security-relevant 3rd party components bundled with Qt

Hi, Does moving the information closer to the code make sense? Most of the information provided in the wiki is already part of the qt_attribution.json files that we use to generate the official documentation about third party modules. What’s missing is the ‘process untrusted content’ flag,

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

> -Original Message- > From: Edward Welbourne > Sent: Wednesday, February 15, 2023 10:45 AM > To: Kai Köhne > Cc: Development@qt-project.org > Subject: Re: Support for *Notes and UpstreamFiles fields in > qt_attributions.json > files > > Kai Köhne (1

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

> -Original Message- > From: Development On Behalf Of Ulf > Hermann via Development > Subject: Re: [Development] Support for *Notes and UpstreamFiles fields in > qt_attributions.json files > > YAML is really quite terrible. If we're going to switch, let's choose > something > else. > >

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

Hi Eddy, > -Original Message- > From: Development On Behalf Of > Edward Welbourne via Development > Sent: Tuesday, February 14, 2023 3:14 PM > To: Development@qt-project.org > Subject: [Development] Support for *Notes and UpstreamFiles fields in > qt_attributions.json files > > Hi all,

Re: [Development] Do we need VS2019 for Qt 6.6?

Hi, We’ve been looking into this. I’m convinced now that the data Vladimir was looking at on the server side is the one shown in the “Compiler Information” in the Telemetry view of Qt Creator. This is the compiler Qt Creator was built with though, not the compiler that Qt Creator uses for

Re: [Development] Qt TextToSpeech: Adding dependency to Qt Multimedia - ok?

Hi, > -Original Message- > From: Development On Behalf Of > [...] > This is a binary compatibility breakage of sorts. Applications that were > linked > against Qt 6.4 or Qt 6.5, and want to run against Qt 6.6 won’t work unless Qt > Multimedia is present. This doesn't violate the binary

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

> -Original Message- >[...] > > MANDATORY > > > > Do not use QT_BEGIN_NAMESPACE ... QT_END_NAMESPACE for example > types. This namespace is exclusively for types in the Qt libraries. > > This is broken. How is one going to correctly forward declare Qt names > in a namespaced build of

Re: [Development] Stickman animation example removed from qtbase in Qt 6

> From: Development On Behalf Of Shawn > Rutledge > >> On 2022 Aug 17, at 09:57, Rasool, Ansar >> wrote: >> >> Hi All,  >> >> It seems that Stickman and many other widget animation examples from qtbase >> has been removed in Qt6 as compared to Qt5. Is there

Re: [Development] Proposal: move Qt provisioning scripts and 3rd party components into a dedicated repo

> -Original Message- > From: Development On Behalf Of > Volker Hilsheimer > [...] > I think that’s by far the exception though. Most 3rd party components we > use have well defined, stable APIs. I think it's the other way round, at least if you go by the number of qt_attribution.json

[Development] Nominating Andreas Eliasson as Approver

has also been actively reviewing other people's documentation patches. So, I see little reason to wait much longer before making him an approver, also because getting another documentation approver would be handy in the upcoming vacation season Kai -- Kai Köhne, Director R | The Qt Company

Re: [Development] [Interest] Issues with latest Qt MaintenanceTool and Kaspersky

> -Ursprüngliche Nachricht- > [...] > Is there a reason to be using a vbs file ? In windows a running executable > cannot replace itself, but it can rename itself. [...] Hi Julien, I don't know the exact reasons why the .vbs approach was chosen. I now filed

Re: [Development] [Interest] Issues with latest Qt MaintenanceTool and Kaspersky

Hi, > Are deferredrenamekERbOS.vbs and deferredrenameQIoNFA.vbs included in the > MaintenanceTool package? They are not _included_ in the MaintenanceTool package. Anyhow, "deferredrenameXX.vbs”are temporary files the MaintenaceTool.exe writes to schedule an update of itself. That is,

Re: [Development] Qt UDL operators

> From: Development On Behalf Of Sona > Kurazyan > Sent: Wednesday, March 30, 2022 3:44 PM > To: Marc Mutz ; development@qt-project.org > Subject: [Development] Qt UDL operators > > [...] > As you can see, https://codereview.qt-project.org/c/qt/qtbase/+/401604 raised > a lot of discussion, and

Re: [Development] Requesting forward BC exception for QtWaylandCompositor in 6.2 and 5.15

> -Original Message- > From: Development On Behalf Of > Giuseppe D'Angelo via Development > [...] > For instance, QtTestLib is not under BC promises. Various modules in their > "Tech preview" state weren't. I really don't know about the specific module... This is tracked in

[Development] Blog post about contributions to Qt repositories in 2021

used to get the numbers: https://git.qt.io/kakoehne/qtprojectstats/-/blob/main/qtprojectstatistics.py Regards Kai -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Str. 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft

Re: [Development] Documentation of new Qt features in qtdoc

> From: Development On Behalf Of Edward > Welbourne > Sent: Monday, November 22, 2021 8:08 PM > To: Shawn Rutledge ; Oswald Buddenhagen > > Cc: development@qt-project.org > Subject: Re: [Development] Documentation of new Qt features in qtdoc > [...] > Shawn Rutledge (22 November 2021 15:56)

[Development] Documentation of new Qt features in qtdoc

Hi, Can we agree to document new features in Qt 6.3 and following released directly in qtdoc.git? We have traditionally been using wiki.qt.io to collect new features in a Qt release, see for instance https://wiki.qt.io/New_Features_in_Qt_6.2. At some time before a release, we started to

Re: [Development] Documentation test builds in CI

Hi Topi, Great news! This should save us quite some time hunting down qdoc errors  Kai From: Development On Behalf Of Topi Reiniö Sent: Thursday, October 21, 2021 9:41 PM To: development@qt-project.org Subject: [Development] Documentation test builds in CI Hello! The testing cycle in Qt's CI

[Development] MSVC warnings in Qt module code now fatal

Hi, Just a heads up that yesterday https://codereview.qt-project.org/c/qt/qtbase/+/356259 went into dev. This makes builds with -warnings-are-errors actually fail for MSVC compiler warnings again. I tested a local qt5.git build beforehand. Anyhow, if you still run into a submodule where

Re: [Development] Renamed: Running a service for Qt community

> From: Development On Behalf Of Benjamin > TERRIER > Subject: Re: [Development] Renamed: Running a service for Qt community > > On Thu, 20 May 2021 at 17:18, Jason H wrote: > >> Anyway, these issues aren't insurmountable, apparently they can be changed >> with the

Re: [Development] Changes to Freenode's IRC

> -Original Message- > From: Jason H > Subject: Re: RE: [Development] Changes to Freenode's IRC > > > > Can we agree to keep the bashing out of this channel? > > You raise important questions. First, what is "bashing", and where is it > appropriate? Or, as I see my behavior, where is

Re: [Development] Changes to Freenode's IRC

> -Original Message- > From: Development On Behalf Of Jason H > Sent: Wednesday, 19 May 2021 17:26 > To: giuseppe.dang...@kdab.com > Cc: development@qt-project.org > Subject: Re: [Development] Changes to Freenode's IRC > > Aren't all the kids these days moving to Discord? Slack is

Re: [Development] Raising minimum CMake version to 3.16 for Qt6

> -Original Message- > I'm not really remembering at the moment. The development hosts were > already set to GCC9 for 6.0. So maybe GCC8 works, but we're not testing it > anywhere (and that makes it basically unsupported). Well, we're still building things on Windows with gcc 8.1. See

[Development] New git submodule qlitehtml in qttools/dev

, please run git submodule update --init --recursive inside qttools. Regards Kai -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Straße 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht

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

> -Ursprüngliche Nachricht- > Von: Development Im Auftrag von > Joerg Bornemann > Gesendet: Freitag, 26. Februar 2021 13:36 > An: Elvis Stansvik > Cc: Macieira, Thiago ; Qt development mailing > list > Betreff: Re: [Development] Qt 6 co-installability with Qt 5 > > On 2/24/21 8:54

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

> Von: Development Im Auftrag von Lisandro > Damián Nicanor Pérez Meyer > Gesendet: Mittwoch, 17. Februar 2021 13:33 > An: development@qt-project.org > Betreff: Re: [Development] Qt 6 co-installability with Qt 5 > > Hi! > El mié., 17 feb. 2021 05:33, Joerg Bornemann

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

> -Ursprüngliche Nachricht- > Von: Development Im Auftrag von > Jyrki Yli-Nokari > Gesendet: Dienstag, 16. Februar 2021 06:10 > An: development@qt-project.org > Betreff: Re: [Development] Qt 6 co-installability with Qt 5 > > Thiago is right. Qt’s biggest problem is the barrier of entry.

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

> -Original Message- > [...] > So why do we even ship 3rd parties with Qt in the current form if we > can't be bother to update them promptly (for bug fixes, security fixes, and > the like)? > Wouldn't it be better to just provide a script (cmake's external > project, recipe, conan

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

> -Original Message- > From: Development On Behalf Of > Thiago Macieira > Sent: Thursday, December 10, 2020 3:48 PM > To: development@qt-project.org > Subject: Re: [Development] Qt 6 co-installability with Qt 5 > > On Wednesday, 9 December 2020 23:2

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

> -Original Message- > From: Development On Behalf Of > Lisandro Damián Nicanor Pérez Meyer > [...] > > We do that already, it's just not enough for user-facing applications. I'll > > be > more verbose on the bug report if needed. > > The problem of options 2 and 3 are that they do not

Re: [Development] Long-lived P1 issues

> From: Development On Behalf Of NIkolai > Marchenko > Sent: Friday, December 4, 2020 9:45 AM > Subject: Re: [Development] Long-lived P1 issues > >> Currently, there are 1175 open P1 issues in the QTBUG project.  583 of those >> issues had that priority set more than one year ago,   > > I am

Re: [Development] Long-lived P1 issues

> -Original Message- >[...] > > (Clicking the ? button next to the priority field in Jira shows the > > following definition for P1: "Urgent and Important, will STOP the > > release if matched with set FixVersion field. This includes > > regressions from the last version that are not edge

[Development] Qt Assistant (was: RE: Qt 6 co-installability with Qt 5)

> -Original Message- > From: Kai Pastor, DG0YT > Sent: Thursday, November 19, 2020 8:27 AM > To: Kai Köhne ; development@qt-project.org > Subject: Re: [Development] Qt 6 co-installability with Qt 5 > > Am 19.11.20 um 08:20 schrieb Kai Köhne: > >> Am 18.11

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

> -Original Message- > From: Development On Behalf Of Kai > Pastor, DG0YT via Development > Sent: Thursday, November 19, 2020 7:03 AM > To: development@qt-project.org > Subject: Re: [Development] Qt 6 co-installability with Qt 5 > > Am 18.11.20 um 15:50 schrieb K

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

> -Original Message- > From: Development On Behalf Of > Thiago Macieira >> On Tuesday, 17 November 2020 00:46:32 PST Joerg Bornemann wrote: >> It is certainly possible to add a further configure option a la >> -qt-executable-suffix -qt6 >> to move the burden from the packagers to

Re: [Development] Installer/Marketplace/Package Manager

Hi Giuseppe, I agree that the current situation is somewhat complicated. But the approach piloted at https://www.qt.io/blog/qt-6-additional-libraries-via-package-manager hopefully will help to tell a more aligned story in the future, at the price of (temporarily) adding yet another way of

Re: [Development] http://download.qt.io/new_archive/qt/

Hi, We noticed the same. It seems a sync'ing issue, I created https://bugreports.qt.io/browse/QTQAINFRA-3944. Kai > -Ursprüngliche Nachricht- > Von: Development Im Auftrag von > Konstantin Tokarev > Gesendet: Freitag, 2. Oktober 2020 14:41 > An: Qt Project Development Mailing-List >

Re: [Development] "Examples and demos" component in Jira (QTBUG project)

> -Ursprüngliche Nachricht- > Von: Development Im Auftrag von > Santtu Ahonen > Betreff: Re: [Development] "Examples and demos" component in Jira (QTBUG > project) > > Retiring the component would be a massive loss of data and alignment > between projects. This before retirement proposal

Re: [Development] [baremetal] Integration of bare-metal C-SPY debugger from IAR EW to QtCreator

Hi Denis, Thanks for the initiative! Give us some time to raise the matter with them  Kai Von: Development Im Auftrag von Denis Shienkov Gesendet: Mittwoch, 26. August 2020 08:38 An: development@qt-project.org Cc: Qt HJK Betreff: Re: [Development] [baremetal] Integration of bare-metal C-SPY

Re: [Development] Where's the dev headers check and -Werror build?

> -Ursprüngliche Nachricht- > Von: Development Im Auftrag von > Thiago Macieira > Gesendet: Mittwoch, 26. August 2020 04:58 > An: development@qt-project.org > Betreff: [Development] Where's the dev headers check and -Werror build? > >

Re: [Development] ChangeLog script will need adaptation to cherry-pick model

> -Ursprüngliche Nachricht- > Von: Development Im Auftrag von > Betreff: Re: [Development] ChangeLog script will need adaptation to cherry- > pick model > > Jani Heikkinen (11 August 2020 07:09) > > if the correct behavior is the first one then the script doesn't need any > change? > >

Re: [Development] Stepping down as QtWebChannel maintainer

Hi, Thanks Arno for stepping up! +1 from my side for both nominations (Approver and Maintainer). And thanks, Milian, for having created & maintained the module for such a long time  > -Ursprüngliche Nachricht- > Von: Development Im Auftrag von > Arno Rehn > Gesendet: Mittwoch, 17.

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

> -Ursprüngliche Nachricht- > Von: Development Im Auftrag von > [...] > To build autotests, -DFEATURE_developer_build=ON will do that right? And > there are also BUILD_TESTING and QT_NO_MAKE_TESTS so what’s the > relationship? It's currently the same as with qt 5: *

[Development] Documenting Qt 6 API breakages

. Thoughts? Kai -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Straße 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B

Re: [Development] MaintenanceTool and/or InstallerFramework horribly insecure?

Hi Konrad, thanks for the report. Volker forwarded it to the qt-project security mailing list. Feel free to send further security related issues there. > When I call MaintenanceTool to install another version of Qt it wants to sudo into root when it starts to download Qt components. It still

[Development] On how to deprecate API

more? Regards Kai -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Straße 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 1443

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

te Thanks for participating! Kai > -Original Message- > From: Development On Behalf Of Kai > Köhne > Sent: Monday, February 24, 2020 4:31 PM > To: Ville Voutilainen ; Lars Knoll > > Cc: Thiago Macieira ; Qt development mailing > list > Subject: Re: [Developm

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

Hi, Since this is arguably as much about taste as it is about technicalities, I thought it might be interesting to do a quick poll in the form of a survey: https://www.1ka.si/a/255723 Disclaimer: Qt Project is not a democracy, so let's not pretend that whatever gets most clicks gets

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

every C++ IDE and tool does accept (and could even check for) ... Kai [1]: In C++11, gcc and clang seem to still warn. However, there are options to disable this. > -Original Message- > From: Development On Behalf Of Kai > Köhne > Sent: Thursday, February 20, 2020 2:44 P

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Development On Behalf Of > Marc Mutz via Development > Sent: Saturday, February 15, 2020 3:24 PM > To: development@qt-project.org > Subject: [Development] A modest proposal: disable lower-case keywords > (emit, foreach, forever, signals, slots) by default > >

Re: [Development] Changes to Qt offering

> Von: Development Im Auftrag von NIkolai > Marchenko > Gesendet: Montag, 27. Januar 2020 16:27 > An: Ville Voutilainen > Cc: Qt development mailing list > Betreff: Re: [Development] Changes to Qt offering > >>  they will be available 12 months after their commercial release  > > That's 12

[Development] Nomination of Build System Maintainer(s)

://codereview.qt-project.org/dashboard/1000120 Alexandru: https://codereview.qt-project.org/dashboard/1004184 Regards Kai [1] See https://wiki.qt.io/Maintainers -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Straße 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha

Re: [Development] Qt 5.14 MinGW debug build doesn't add debug suffix

> -Original Message- > From: Development On Behalf Of > Thiago Macieira > Sent: Tuesday, January 14, 2020 4:33 PM > To: development@qt-project.org > Subject: Re: [Development] Qt 5.14 MinGW debug build doesn't add debug > suffix > > On Tuesday, 14 January

Re: [Development] Qt 5.14 MinGW debug build doesn't add debug suffix

> From: Development On Behalf Of Dmitriy > Purgin > Sent: Tuesday, January 14, 2020 8:46 AM > To: Thiago Macieira > Cc: Qt development mailing list > Subject: Re: [Development] Qt 5.14 MinGW debug build doesn't add debug suffix > > I've just discovered another side-effect of this change. I've

Re: [Development] QtCS2019 Notes from "Fuzzing Qt" BoF session

> -Original Message- > From: Development On Behalf Of > Oswald Buddenhagen > Sent: Thursday, November 21, 2019 2:41 PM > To: development@qt-project.org > Subject: Re: [Development] QtCS2019 Notes from "Fuzzing Qt" BoF session > > On Thu, Nov 21, 2019 at 12:13:55PM +, Robert Loehning

Re: [Development] QtCS2019 Notes: Clang-based cpp parser for lupdate

> -Original Message- > From: Development On Behalf Of > Joerg Bornemann > Sent: Friday, November 22, 2019 1:25 PM > To: Kai Pastor, DG0YT ; development@qt-project.org > Subject: Re: [Development] QtCS2019 Notes: Clang-based cpp parser for > lupdate > > On 11/22/19 7:21 AM, Kai Pastor,

[Development] Notes from "Releasing" session in QtCon19

c (AP Jani Heikkinen) Greetings from Berlin! Kai [1]: https://bugreports.qt.io/secure/Dashboard.jspa?selectPageId=15911 -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Straße 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellscha

Re: [Development] Qt Contributors' Summit 2019 - Registration open!

> -Original Message- > From: Bogdan Vatra > Sent: Tuesday, September 24, 2019 11:14 AM > To: development@qt-project.org > Cc: Kai Köhne > Subject: Re: [Development] Qt Contributors' Summit 2019 - Registration open! > > Hi, > > Considering that Qt

[Development] Qt Contributors' Summit 2019 - Registration open!

Kai -- Kai Köhne, Director R | The Qt Company The Qt Company GmbH, Erich-Thilo-Straße 10, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B

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

Hi Florian, We'll run the Contributor Summit in Berlin Adlershof. I started to create a wiki page for this, expect more updates in the next days! https://wiki.qt.io/Qt_Contributors_Summit_2019 Regards Kai > -Original Message- > From: Development On Behalf Of > Florian Bruhin > Sent:

Re: [Development] Dropping MinGW support in Qt 6 (Was: HEADS-UP: QStringLiteral)

> Anyway, my ultimate goal is to create and distribute my Qt apps the same > way as Qt's installation program (you can tell I really admire that > program a lot :-) > i.e. link *everything* statically and build myself a ~ 20 MB humongous > .exe file (which only needs msvcrt.dll). And that kind of

[Development] Qt PDF as a new TP module for Qt 5.14

Hi, I suggest to promote Qt PDF to a Qt module. For Qt 5.14, it will be in Tech Preview state, and Shawn Rutledge is volunteering to be the maintainer. Although still staying an independent library from the user's perspective, it will be hosted and built in the qtwebengine.git repository.

Re: [Development] Proposing CMake as build tool for Qt 6

> -Original Message- > From: Development On Behalf Of > Palaraja, Kavindra > Sent: Thursday, June 6, 2019 3:38 PM > To: development@qt-project.org > Subject: Re: [Development] Proposing CMake as build tool for Qt 6 > > Hi, > > Just curious, do you have a link to what the draft

Re: [Development] Qt XML and Qt Xml Patterns

> -Original Message- > From: Development On Behalf Of > Bernhard Lindner > Subject: Re: [Development] Qt XML and Qt Xml Patterns > > > It's good that Bernhard has received an official statement. > > I agree! Thank you! Indeed, thanks for bringing this up here! We quite obviously should

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

> -Original Message- > From: Development On Behalf Of > Florian Bruhin > Sent: Monday, May 20, 2019 10:50 AM > To: development@qt-project.org > Subject: [Development] Proposal: Using Gerrit for new approver proposals? >[...] > What about using Gerrit to do so? I'm not sure how the

Re: [Development] Assistant WebKit/WebEngine support

> -Original Message- > From: Development On Behalf Of > Subject: [Development] Assistant WebKit/WebEngine support > > Hi, > > I am prepared to do some work on Qt Assistant, and I'd like to know how that > will be received. Cool, great you want to tackle this  I'm sure Jarek (the

Re: [Development] [Interest] Qt World Summit 2019 - CfP

useppe > D'Angelo via Interest > Sent: Thursday, May 2, 2019 11:01 AM > To: inter...@qt-project.org > Subject: Re: [Interest] Qt World Summit 2019 - CfP > > Hi, > > On 23/04/2019 11:49, Kai Köhne wrote: > > For Berlin, we (again) have an open Call for Presentations. The d

[Development] Qt World Summit 2019 - CfP

Hi, In case anybody missed it so far - Qt World Summit 2019 will happen on 4-6 November in Berlin, and 28, 29 November in Tokyo: https://www.qt.io/qtws19/home For Berlin, we (again) have an open Call for Presentations. The deadline for submissions is already *3rd of May* - that is, Friday