Re: [Development] What are differences/relations among CMake targets with "docs" word?

, but there are lots of Warning Messages when building html_docs(_xxx). > For > example, warning: Can't link to 'index.html' > > > > --- > Haowei Hsu > -- > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development --

Re: [Development] Creator: how to search for qdoc

> Am 28/02/2023 um 09:20 schrieb Eike Ziller via Development > : > > Hi, > >> Am 27/02/2023 um 17:34 schrieb Lisandro Damián Nicanor Pérez Meyer >> : >> >> Hi! >> >> In Qt Creator qdoc is being searched by assuming that it is in the sam

Re: [Development] Creator: how to search for qdoc

> -- > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha

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

> Am 04/02/2023 um 00:08 schrieb Thiago Macieira : > > On Friday, 3 February 2023 06:00:25 PST Kai Köhne via Development wrote: >> 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

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

> 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 and to the >>> point. Do not

Re: [Development] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops

onsider keeping Mac OS 10.15 as a target. > Thanks. > > Kind regards, > Robert Iakobashvili > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/develop

Re: [Development] Using QtCreator for Qt development

Creator 9.0) where > the tests could be selected. https://doc.qt.io/qtcreator/creator-autotest.html But, it took so long "Scanning for tests" that I didn't wait for it to finish... > Meanwhile I've opened suggestion > https://bugreports.qt.io/browse/QTCREATORBUG-28590  -- Eike

Re: [Development] Using QtCreator for Qt development

turn individual test on for the build? Anyway, with both on, you can just choose a test to run & debug. It looks like our autotest integration (the separate "Tests" panel) takes ages looking for tests, but running tests directly as normal run configurations works fine. Qt also has some

Re: [Development] Proposal: let's change the release schedules a bit

o FF for April release would be in > January and FF for October release would be in August. > > Any opinions or objections? > > br, > Jani > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org

Re: [Development] Nominating Marcus Tillmanns as Approver

> Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://qt.i

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

ch is similar to the issues of #pragma once. Header guards do have downsides too, but I suppose software developers got used to them and have the necessary workarounds in place. Which is a valid argument for not introducing #pragma once in Qt, which would require different workarounds, and c

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

e. But perhaps I’m missing > something. Does anything speak against using ‘#pragma once’ in new files? Just for reference, we are using it without issues in Qt Creator since 2016. (But of course our platform and compiler requirements are more restricted than for Qt.) -- Eike Ziller Principal So

Re: [Development] QKeySequenceEdit questions

lass to handle a specific key event to finish editing), >> then patches welcome. > > The list of properties that I think a generic hotkey editor would need: > > 1. Single combination > 2. Finishing character > 3. No timer! This could be done automatically for keyPressE

Re: [Development] QKeySequenceEdit questions

, the > timer still gets in the ideal way, although it will be better than what we > have now. It will not still be ideal though. > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/developm

Re: [Development] Importing a module build in creator

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

Re: [Development] Importing a module build in creator

configure options for the module. (In the end it calls qt-cmake-private with a few more CMake variables.) I.e. better use qt-configure-module to configure modules. That probably gets some edge cases right, that aren’t covered by just qt-cmake-private. -- Eike Ziller Principal Software Enginee

Re: [Development] Importing a module build in creator

___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Var

Re: [Development] Mirror IRC channels on KDE's Matrix Instance

discussion of other communication platforms outside >>>>> this thread, while they might be valid, it's out of the scope of this >>>>> proposal. >>>>> >>>>> Question >>>>> ---- >>>>> >>>>>

Re: [Development] Qt website showing template

plate. Can you fix the link or restore the home page? > Refer to the screenshot below: > > > > Thanks & Regards, > Nibedit > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/d

Re: [Development] Changes to Freenode's IRC

> a > _requirement_ it's an absolute no-go. > >> If anything we should have more verification in our chat. We run Qt Project >> as a >> meritocracy where it is important that someone is who they say they are >> (like a >> maintainer). > > I d

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

e > > Kind regards, > Robert Iakobashvili > .... > > On Fri, May 7, 2021 at 1:12 PM Eike Ziller wrote: >> >> >> >>> On May 7, 2021, at 11:47, Tor Arne Vestbø wrote: >>> >>> Qt 6.0 and above has official suppor

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

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

Re: [Development] Repository request: qlitehtml

itehtml unrealistic. That said, moving the source out of Qt Creator makes it easier to extend and adapt it to different parties’ needs too. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pä

Re: [Development] Repository request: qlitehtml

> On Jan 19, 2021, at 16:30, Eike Ziller wrote: > > Hi, > > I’d like to request a new repository on codereview.qt-project.org > > Name and description: qlitehtml - Lightweight HTML/CSS viewer for Qt, using > litehtml (https://github.com/litehtml/litehtml) > Resp

[Development] Repository request: qlitehtml

Hi, I’d like to request a new repository on codereview.qt-project.org Name and description: qlitehtml - Lightweight HTML/CSS viewer for Qt, using litehtml (https://github.com/litehtml/litehtml) Responsible person: Eike Ziller (eike.zil...@qt.io) Desired repository name: playground/qlitehtml URL

Re: [Development] Qt6 repo

this can then require a different qtbase SHA to build. Exactly this situation occurred multiple times to me during (even late) Qt6 development. qt5.git integrations are the only “guaranteed” collection of SHAs that build. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thil

Re: [Development] Long-lived P1 issues

> On Nov 3, 2020, at 12:56, Eike Ziller wrote: > > > >> On Nov 3, 2020, at 11:34, Alex Blasche wrote: >> >> >> >>> -Original Message- >>> From: Development On Behalf Of >>> Jason McDonald >> >>>

Re: [Development] Long-lived P1 issues

> On Nov 3, 2020, at 11:34, Alex Blasche wrote: > > > >> -Original Message- >> From: Development On Behalf Of >> Jason McDonald > >> Looking at the huge list of P1s we have right now, I have absolutely no idea >> what issues are genuinely blocking Qt 6.0 or if there are any that I

Re: [Development] Long-lived P1 issues

> On Nov 3, 2020, at 09:07, Ulf Hermann wrote: > >> Currently, there are 1175 open P1 issues in the QTBUG project. 583 of those >> issues had that priority set more than one year ago, 342 of those had their >> priority set more than two years ago, and 175 of those more than three years >>

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

Just as a note we are using markdown for Qt Creator changelogs since a long time too. With the “right” heading styles it is also nicely readable in ASCII. You can actually use ### as the third level of headings without compromising readablility.

Re: [Development] Applications using -fno-rtti

ting. If you use Q_OBJECT throughout your class hierarchy, qobject_cast is available anyhow. So, the argument that Q_OBJECT makes it safe to use dynamic_cast reads a bit strange. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 B

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

> On Jun 9, 2020, at 12:07, Eike Ziller wrote: > > > >> On Jun 9, 2020, at 09:59, Andy Nichols wrote: >> >> Hi Alexandru, >> >> I think Brett touches on the biggest blocker for me and that is actually >> related to Qt Creators ability to o

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

e.txt contains the correct entry, and that compiler is actually already registered in Qt Creator. The Qt version in the kit is empty too. Detecting that seems to be a bit more difficult, but since CMake gives us the relevant include paths anyhow that might not be such an issue. -- Eike Ziller Pr

Re: [Development] mobile-to-mobile connection for p2p game

> Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsfü

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

that you can code complete for signals even in an IDE that doesn’t have explicit support for connect(...) or any Qt. Maybe difficult to adapt in Qt.) 6. finished(); ? I don’t know, but since 3, 4, and 6 are already open to anyone now, I don’t think we need 1 or 2, or (n+1) > >> Cheers, &

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

g >> https://lists.qt-project.org/listinfo/development > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH

Re: [Development] The future of smart pointers in Qt API

> Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha V

Re: [Development] sdktool parameters

-supportedAbis arm-linux-generic-elf-32bit \ >ProjectExplorer.GccToolChain.PlatformCodeGenFlags QStringList: > '-mthumb’, '-mfpu=neon-vfpv4', 'mfloat-abi=hard’, '-mcpu=cortex-a7’ > > Best regards, Yury Lunyov. > ___ > Develop

Re: [Development] Assistant WebKit/WebEngine support

tle, finding text and getting the selected content, and callbacks/signals for loading resources and reacting to clicks. This part is completely independent from Qt Creator and could be used elsewhere. Additionally there is a viewer backend implementation for Qt Creator that uses this widget.

Re: [Development] QTCS2019 Notes from QtQml session

> On 25. Nov 2019, at 11:03, Giuseppe D'Angelo via Development > wrote: > > Il 25/11/19 10:25, Eike Ziller ha scritto: >>> ? >> Similar things can happen in C++ with method names. >> C++ got the ‘override’ keyword to make these breakages detectable by tooling

Re: [Development] RFC: QVariant changes in Qt6

e proposed replacement for the deprecated methods is introduced late in the process, which makes porting harder, and as Olivier says, for no obvious reason. qvariant_cast also is consistent with the other “casts” in Qt and C++. > >>> 6. QVariant::Type and QMetaType::Type enums >>> >>> QVariant::Type is already marked

Re: [Development] QTCS2019 Notes from QtQml session

d names. C++ got the ‘override’ keyword to make these breakages detectable by tooling. It looks to me like the case id==propertyname would also be detectable by tooling? Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io h

Re: [Development] RFC: Defaulting to or enforcing UTF-8 locales on Unix systems

er (for e.g. the manifest file), and RCC of course. >> Why does Qt Creator need other codecs? Qt Creator is a generic text editor. A generic text editor is expected to be able to read and write files in different encodings. -- Eike Ziller Principal Software Engineer The Qt Company

Re: [Development] RFC: Defaulting to or enforcing UTF-8 locales on Unix systems

UTF-8) >qFatal("Qt only supports UTF-8 locales. " > "Please configure your system properly"); > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel System Software Products > > > > ___ > Develo

Re: [Development] Two-digit dates: what century should we use ?

> On 6. Nov 2019, at 13:38, Edward Welbourne wrote: > > Eike Ziller (6 November 2019 09:45) >> It sounds to me like any automatically chosen base for 2-digit years >> will be wrong depending on use case. > > You (among several others) make a compelling case

Re: [Development] Two-digit dates: what century should we use ?

as anyone a better suggestion for how to chose a rolling range ? > * Should we have a buffer ? If so, how wide ? > * How far into the past and future should the range reach ? > > Eddy. > ___ > Development mailing list > Developm

Re: [Development] Property bindings in Qt 6

ve to write the special code that does whatever you want to do with the property when it changes, also with the initial value. (sodium even has transactions, but that’s a different story ;) ) > So I've used knockout and observables, and at the same time used Qt, and I > always preferred

Re: [Development] Property bindings in Qt 6

possible. Ulf has been working towards > this from the QML engine direction (see the recent email about moc and > meta-type extraction) and Fabian has been working on the QML linter as a > starting point towards a compilation model for QML. > > > This is our rough plan of how we

Re: [Development] Qt Creatror can require a patched Clang build?

mián Nicanor Pérez Meyer > http://perezmeyer.com.ar/ > http://perezmeyer.blogspot.com/ > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal

Re: [Development] Qt Creatror can require a patched Clang build?

> On 10. Sep 2019, at 13:18, Lisandro Damián Nicanor Pérez Meyer > wrote: > > Hi! Let me put some other perspective into this. > > On Tue, 10 Sep 2019 at 07:35, Eike Ziller wrote: >> >> To put some perspective on this: >> >> The ClangFormat plugin

Re: [Development] Qt Creatror can require a patched Clang build?

> Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft

Re: [Development] Supported compilers for Qt 6

c-clang we already pretty much >> assume clang-cl 8. But we have not automated testing of non-apple clang, so >> it >> often breaks due to extra warnings or genuine clang bugs. > > Yes. It would be good to have a build using standard clang in CI in the > future. But that’s a separa

Re: [Development] Assistant WebKit/WebEngine support

> On Jun 28, 2019, at 14:46, Palaraja, Kavindra wrote: > > On 28.06.19, 12:22, "Eike Ziller" wrote: > > > >> From your response, I'm only gathering two options: > >There are other options. >https://lists.qt-project.org/

Re: [Development] Assistant WebKit/WebEngine support

> On Jun 28, 2019, at 10:56, Palaraja, Kavindra wrote: > > On 28.06.19, 10:24, "Eike Ziller" wrote: > >> On 27. Jun 2019, at 15:46, Palaraja, Kavindra wrote: >> >> On 27.06.19, 10:47, "Development on behalf of Jaroslaw Kobus" >>

Re: [Development] Assistant WebKit/WebEngine support

> On Jun 28, 2019, at 10:24, Eike Ziller wrote: > > > >> On 27. Jun 2019, at 15:46, Palaraja, Kavindra wrote: >> >> On 27.06.19, 10:47, "Development on behalf of Jaroslaw Kobus" >> wrote: >> >> QTextBrowser promises to ren

Re: [Development] Assistant WebKit/WebEngine support

this email or its attachment(s). Furthermore, > you are hereby notified that any dissemination, distribution or copying of > this e-mail and any attachment(s) is strictly prohibited. If you have > received this e-mail in error, please immediately notify the sender by > replying to this e-mail a

Re: [Development] Assistant WebKit/WebEngine support

I did my own assessment of ~70MB per open page on macOS. Context help + Help mode + external window. But we _do_ have the feature of opening new “tabs” in help mode, and these are restored at Qt Creator startup, so it is actually not unrealistic to assume that people have more than 3 viewer instan

Re: [Development] Assistant WebKit/WebEngine support

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

Re: [Development] Assistant WebKit/WebEngine support

tatus quo) and 3 (WebKit) in no particular order. But > since I'm not willing to put in any serious work or pay for it - my vote > does not count - I'm just a user. ;) > > Feel free to correct/critique my assessment and to add more options if > you see any. Otherwise: chose your poi

Re: [Development] Assistant WebKit/WebEngine support

lack many features > that we have on the web based docs. How come we accept that? Using QtWebEngine for that means that 30-40% of Qt Creator is just for viewing help. And 70% or so of that actually would actually not be required for rendering beautiful help pages like in a browser (QtWebKit

Re: [Development] Assistant WebKit/WebEngine support

erver. > > > I think these are all options in the future. > > > Simon > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Softwa

Re: [Development] Assistant WebKit/WebEngine support

> On 24. Jun 2019, at 11:42, Palaraja, Kavindra wrote: > > > On 24.06.19, 11:20, "Eike Ziller" wrote: > > .. > >> Have you seen Qt Creator's Help Integration recently? >> * It doesn't render 1:1 with the default style that is used on >

Re: [Development] Assistant WebKit/WebEngine support

> received this e-mail in error, please immediately notify the sender by > replying to this e-mail and then delete this e-mail and any attachment(s) or > copies thereof from your system. Thank you. > ___ > Development mailing list > Deve

Re: [Development] QList for Qt 6

________ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.io http://

Re: [Development] Views

d > then they will fall back to a raw loop, sometime, in the case of removing, > introducing quadratic complexity. Had the Qt API and the docs not lied to > them by permanently showing contains() without mentioning that it's but a > short-cut for a corner-case, but shown them std::find or s

Re: [Development] Qt online SDK security problems

f Qt users that are using the latest Qt versions is very low… >>> >>> >>> Having said that, pretty please with sugar on top consider to add the >>> >>> needed support to help the users to always use the latest and the safest >&g

Re: [Development] Qt and Metal

___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius,

Re: [Development] On deprecating functions

h and find someone to +2 it". > > The one I suggested in https://codereview.qt-project.org/#/c/254909/ > makes sure that it is noticed at some time, and at that time there > was some period in between where people had a reasonable chance to > update their code base with

Re: [Development] New API design for file system operations

ing from backup” or “downloading from the internet”, I suppose. The context of the top statement here seems to have gotten lost, but “restoring data from the trash” would in the best case be part of the undo stack of the application which you used to trash it, so I’d argue that “restoring data from th

Re: [Development] Looking for Feedback QDeferred

bother you with yet another promise/deferred library for Qt. I am > looking for feedback. > > https://github.com/juangburgos/QDeferred > > Thanks. > ___ > Development mailing list > Development@qt-project.org > https://list

Re: [Development] Proposal: New branch model

Let’s also not forget that Qt 6 is to some extent a temporary problem that >> we’ll have for maximum one year. After that all of Qt 5 is in stable mode >> with bug fixing only. Then we can basically go back to a slightly modified >> cherry-pick mode: Push to dev (Qt6) and cherry-pick into Qt 5.15 for bug >> fixes. If the code base has div

Re: [Development] [Qt-creator] Stepping down as maintainer of project management in Qt Creator

propose Christian Kandeler to take over. He is a capable >>> developer with a deep understanding of the code involved and I am sure >>> he will do a terrific job going forward. >> >> ...that here is very much on the spot, even in my world. >> >> So +1 from

Re: [Development] Missing documentation in Qt 5.12

p through the hierarchy works, but is not very efficient, the all members list is much more convenient. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Ha

Re: [Development] [Qt-creator] Qt 5.12.0 Beta4 released

en >> Release Manager >> >> >> >> >> >> ___ >> Development mailing list >> >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development > >

Re: [Development] Naming convention for (scoped) enums

- describe the pro’s and con’s of scoped enums inside classes >- ask the developer to consider each case individually > - and use good judgement in choosing one or the other Obviously we have a disagreement on what the “good judgement” is supposed to be though ;) -- Eike

Re: [Development] override keyword on destructors

question > becomes whether such changes are likely; I don't think they are, > whereas for functions > other than a destructor such changes are somewhat likely. For example when removing QObject as a base class in a class hierarchy. We regularly do these kind of changes in Qt Creator, when

Re: [Development] Naming convention for (scoped) enums

shouldn’t block us moving >>> forward with #1. >> >> I don't see how a policy of elevating warnings to errors is better that >> using a language inbuilt error due to strong type safety. > > Of course it’s not better, if you focus only on that. The use of a > warning-

Re: [Development] Naming convention for (scoped) enums

> On 14. Aug 2018, at 13:18, Tor Arne Vestbø wrote: > > >> On 14 Aug 2018, at 13:13, Eike Ziller wrote: >> >> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2347.pdf states the >> problems that were the driver for creating strongly typed enu

Re: [Development] Naming convention for (scoped) enums

y to specify underlying type 3. Scoping > that specifically mentions the enum inside a class use case a primary driver? Why would the implicit conversion problem be any different for enums inside a class? > > You conveniently left out this part of my reply: > >>> Clang warns about this with -Wenum-compare

Re: [Development] Monitoring of upstream vulnerabilities

ow does the bind Qt to a private tool? > > I don't want to make a mountain out of a mole hill, but with all the > transparency in Qt, I just expected it to be accessible is all. These tools are currently not used for Qt. Thiago is talking about "what we use in Clear Linux”, where “we

Re: [Development] QtCS 2018: Third-party and security policy

CVEs, we may be shipping code that is vulnerable and not know it. > > I'm not trying to educate users. If someone downstream from us has more lax > policies, it's their business. It's their liability if something happens. > > My problem is those downstream who have more strict

Re: [Development] Changing maintainer-ship for Qt Assistant, Qt Help and Qt Creator’s help Integration

wer Chaussee 13, 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-p

Re: [Development] Changing maintainership for Qt Creator modules

, Mika Harjuaho. Sitz der > Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, > HRB 144331 B > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Eike Ziller Principal Softwar

Re: [Development] Proposing Orgad Shaneh as Maintainer of Version Control modules in Qt Creator

esellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 > B > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Eike Ziller Principal Softw

Re: [Development] New Qt snapshots available

>> Development mailing list >> >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development > > _______ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo

Re: [Development] #pragma once

/wiki/Pragma_once#Caveats >>>> >>>> That wikipedia link seems to describe the problems fairly accurately. >>> >>> Do we have that issue in Qt? >>> >>>>>> and modules are a superior solution anyway. >>>>> How so? &g

Re: [Development] Undeprecating QString::null

o easily. > > But could you please comment on why this change is an improvement - > beyond getting rid of 3-4 lines in qstring.h ? > > Thanks, > Uwe > > > ___ > Development mailing list > Development@qt-project.or

Re: [Development] Nominating Ivan Donchevskii for approver

butions: >> https://codereview.qt-project.org/#/q/owner:%22Ivan+Donchevskii%22,n,z > > +1 > > Especially his contributions to clang itself improved Qt Creator on Windows > greatly! + 1 -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12

Re: [Development] Nominating Lorenz Haas for approver

;> ___ >> Development mailing list >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development > > +1! > > Nikolai > ___ > Development m

Re: [Development] Clazy results for Qt codebase

> On Oct 18, 2017, at 17:51, Sergio Martins <sergio.mart...@kdab.com> wrote: > > On 2017-10-11 08:17, Eike Ziller wrote: >>> On 10. Oct 2017, at 15:41, Sergio Martins <sergio.mart...@kdab.com> wrote: >>> Oops, here's the non-internal URL: >>&g

Re: [Development] Future of QBS

>> >> My 2 cents, >> ___ >> Development mailing list >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development > ___ > Development maili

Re: [Development] Future of QBS

's OK, such is life! :) >> >> What I like with Qbs is the flexibility and its structured yet dynamic >> language (Qml-ish). >> But I'm having scalability and performance issues, that's another story that >> i will report on the Qbs mailing list once i'm back on my

Re: [Development] Clazy results for Qt codebase

> On 10. Oct 2017, at 15:41, Sergio Martins wrote: > > > > Oops, here's the non-internal URL: > https://docs.kdab.com/analysis/qt5/clazy.html > > Thanks Mitch I’d be interested in seeing results for Qt Creator too :) Br, Eike > > On 2017-10-10 14:27, Sergio

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

e for that specific case (maybe adding a funny custom QObjectTimer class for the Qt 5 build). -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Be

Re: [Development] Introducing discussion about QStringFormatter

rammers shall find it a bit heavy-weight (needing a hash, of some > variety, to do simple formatting) but it likely feels much more natural > at the QML level (just as it does in python). With C++11 this can be written as QStringFormatter(“Hello, {name}”).arg({{“name”, “World”}}); which is at

[Development] Nominating Vikas Pachdha for Approver status

Hereby I nominate Vikas Pachdha for Approver status. He has been defacto maintaining iOS support in Qt Creator since a year. https://codereview.qt-project.org/#/q/owner:%22Vikas+Pachdha%22+status:merged,n,z Br, -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee

Re: [Development] Qt 5.9 beta2 available

desktop. > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.

Re: [Development] Proposal to adjust release candidate process

rchitect - Intel Open Source Technology Center > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company G

Re: [Development] RFC: Containers member functions for algorithm

gin-end-cluttered > > erase_if(myList, [&](const auto ) { elem.field > someValue; }); > > and some hope that it going from 'myList' to 'myList()' is really > just two chars change. > > Not Nice (TM). > > Andre' > _

Re: [Development] RFC: Containers member functions for algorithm

ing API to the containers has potential to greatly reduce the bike-shedding. Just add one function that returns a pointer, and another one that returns the iterator, without the fear of bloating the API of every container class. Br, Eike > Regards > -- > Olivier > > Woboq - Qt ser

  1   2   >