Re: [Qt-creator] Nominating André Hartmann as new Maintainer of VCS support in Qt Creator (was: Re: Stepping down as maintainer)
> Am 19.06.2024 um 10:17 schrieb Eike Ziller via Qt-creator > : > > Hi, > > I nominate André Hartmann as the new maintainer of Version Control in Qt > Creator. His contribution history in Qt Creator goes back to 2011 as well, > and he regularly worked on improving our version control support (as well as > contributing to Qt and maintaining qtserialbus/CANBus). > https://codereview.qt-project.org/q/owner:aha_1...@gmx.de +1 for André, I am convinced that Andre is the perfect fit to be a VCS maintainer! Jarek -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Stepping down as maintainer
Hi Orgad, this is sad news. I would like to add that you have been a reviewer of more than 4500 patches coming from other devs. And since you have reviewed many patches coming from me, I can certify that working with you was always a real pleasure. Thank you for your kindness, help and accuracy! Thank you for your invaluable contribution! All the best, Orgad! Jarek From: Qt-creator on behalf of Robert Löhning via Qt-creator Sent: Friday, June 14, 2024 8:48 PM To: qt-creator@qt-project.org Subject: Re: [Qt-creator] Stepping down as maintainer Am 14.06.24 um 18:36 schrieb apoenitz: > On Fri, Jun 14, 2024 at 03:31:00PM +0300, Orgad Shaneh wrote: >> Hi, >> I've been using Qt Creator since its first version and began >> contributing to it in 2011 (with Gitorious :p). When I joined >> AudioCodes, I introduced Qt Creator there, and for many years, most of >> the C++ developers in my team have been using it daily. >> Over the years, I've made numerous contributions to the project, >> reporting 952 bugs and submitting 3,370 commits to Qt Creator. However, >> in recent years, I've been working on a different project which isn't >> written in C++. As a result, I use Qt Creator less frequently and have >> much less time to maintain it. >> I still use and love Qt Creator, and it remains my first choice for >> C++, but I can no longer continue maintaining it. I propose André >> Hartmann or Jarek Kobus as my successors. >> I'll likely stay around and be available for reviews ;) >> Thank you all for this great product! >> - Orgad > > Hi Orgad. > > This is sad news, for the project, and for me personally. > > To the impressive track record I'd like to add marvellous response times > in code reviews and Jira that made working with you a real pleasure. > > Thank you for your work and all the best, > Andre' > Hi Orgad, sad news, indeed. Although, AFAIK, nobody from The Qt Company's Creator team ever met you in person, I guess I'm not the only one who has always felt like you are one of the team, one of us. Thank you very much for your persistence and reliability. Thank _you_ for this great product! Cheers, Robert -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Poll: Contents / styling of editor toolbars
> > 1. I never use what occupies the most of the toolbar, i.e. the > > combobox in the middle, containing the tree of namespaces / classes / > > methods. > > I never use them either, actually. The only thing that I occasionally > looks at it the 'column' information. > > > Maybe this functionality could be merged into "class view" on > > the left side, showing the content of the current editor (instead of > > showing everything from the current project, like it's now - probably > > it could be configurable). > > One could think of making "any" action from Environment->Keyboard > "pinnable" to the toolbar. But would /you/ actually /use/ it, > instead of triggering it by the keyboard shortcut? The thing is that I don't have a good memory when it comes to shortcuts, especially when I don't trigger them a couple of times a day. For most often actions I remember just couple of shortcuts. The issue with shortcuts is sometimes that I don't know how to trigger them, even when I see it. E.g. I would love to use a shortcut for "Tools | Git | Current File | Diff", for which the shortcut is: "Alt+G, Alt+D". This means you need to press (exactly in this order), without releasing any key in meantime: Alt key, G key, D key. Then you may release all 3 keys. Very cumbersome. If you do it like: Alt key, D key (and you are about to press the 3rd G key), a "Debug" menu is being open instead (since the Alt D accelerator). -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Poll: Contents / styling of editor toolbars
> > 3. I would replace the current weird icon for "Remove Split" in the > > top right corner with the "X" icon. Not sure what to do with the "X" > > icon next to the filename combobox, though. But it should be rather > > clear that "X" next to the filename means we close the filename (in > > all splits), with "X" in the top right corned means we close the > > window (i.e. close the split). > > "How" make this clear? > > Ok, I am using FakeVim, I personally really /never/ look up there, > it's all vsp/sp/Ctrl-W for me, so I don't really know > what an icon with a "good" visual hint looks like. Is [x] a good > enough hint for "get rid of $thing, whatever $thing is" ? I just wanted to make a note that nearly always a window / dock / something "closable" has a "X" button in the top right corner and it's intuitive that this "X" closes it. Having a different icon for this action introduces an unneded delay in ergonomics I guess. From: A. Pönitz Sent: Tuesday, April 4, 2023 7:53 PM To: Jaroslaw Kobus Cc: qt-creator@qt-project.org; Friedemann Kleint Subject: Re: [Qt-creator] Poll: Contents / styling of editor toolbars On Tue, Apr 04, 2023 at 05:34:30PM +, Jaroslaw Kobus via Qt-creator wrote: > 1. I never use what occupies the most of the toolbar, i.e. the > combobox in the middle, containing the tree of namespaces / classes / > methods. I never use them either, actually. The only thing that I occasionally looks at it the 'column' information. > Maybe this functionality could be merged into "class view" on > the left side, showing the content of the current editor (instead of > showing everything from the current project, like it's now - probably > it could be configurable). One could think of making "any" action from Environment->Keyboard "pinnable" to the toolbar. But would /you/ actually /use/ it, instead of triggering it by the keyboard shortcut? > 2. I never use encoding combo, which also occupies some place, so I'd > hide it deeper (maybe inside file menu?) Ok... > 3. I would replace the current weird icon for "Remove Split" in the > top right corner with the "X" icon. Not sure what to do with the "X" > icon next to the filename combobox, though. But it should be rather > clear that "X" next to the filename means we close the filename (in > all splits), with "X" in the top right corned means we close the > window (i.e. close the split). "How" make this clear? Ok, I am using FakeVim, I personally really /never/ look up there, it's all vsp/sp/Ctrl-W for me, so I don't really know what an icon with a "good" visual hint looks like. Is [x] a good enough hint for "get rid of $thing, whatever $thing is" ? > 4. I would add much more actions for text editing, like "to lower / > upper", "visualize spaces", etc..., which are currently deeply hidden > in menu structure or in settings. Make it configurable? This is close to the first request, right? Andre' -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Poll: Contents / styling of editor toolbars
1. I never use what occupies the most of the toolbar, i.e. the combobox in the middle, containing the tree of namespaces / classes / methods. Maybe this functionality could be merged into "class view" on the left side, showing the content of the current editor (instead of showing everything from the current project, like it's now - probably it could be configurable). 2. I never use encoding combo, which also occupies some place, so I'd hide it deeper (maybe inside file menu?) 3. I would replace the current weird icon for "Remove Split" in the top right corner with the "X" icon. Not sure what to do with the "X" icon next to the filename combobox, though. But it should be rather clear that "X" next to the filename means we close the filename (in all splits), with "X" in the top right corned means we close the window (i.e. close the split). 4. I would add much more actions for text editing, like "to lower / upper", "visualize spaces", etc..., which are currently deeply hidden in menu structure or in settings. Make it configurable? From: Qt-creator on behalf of Friedemann Kleint via Qt-creator Sent: Tuesday, April 4, 2023 7:05 PM To: qt-creator@qt-project.org Subject: Re: [Qt-creator] Poll: Contents / styling of editor toolbars Hi, files in tabs, please... Regards, Friedemann -- Friedemann Kleint The Qt Company GmbH -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Utils::QtcProcess
>> 2. When using QtcProcess it is also safe to destruct it while underlaying >> QProcess is still being run. QtcProcess takes care about safe termination >> through Utils::ProcessReaper in the background. > > What does this do other than terminating the process? How is this more safe? > Can/should this be upstreamed to QtCore if it's such a general important > improvement? When you destruct running QProcess, it: 1. Prints a warning 2. Calls kill() 3. Calls blocking waitForFinished() - this may possibly block your UI thread for longer time. When you destruct running QtcProcess, it: 1. Doesn't print a warining 2. Moves a running process into another thread (ProcessReaper's thread) 3. Calls terminate (a gentle way of stopping the process) 4. After desired time (500ms by default), when process didn't finish, it calls kill() 5. The destructor of QtcProcess doesn't block at all. 6. When the ProcessReaper is being destructed (when leaving main() function) it waits until all processes being reaped are finished inside a ProcessReaper. Not sure if the above solution may be easily adopted by QProcess, as the latter is designed to work also without an event loop, while the current implementation of ProcessReaper relies on having spinning event loop. However, maybe it can be easily bypassed somehow. Feel free to open a ticket for QProcess feature, if you find it useful. Jarek -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Utils::QtcProcess
Hi, QtcProcess is a wrapper around QProcess. It has some advantages over the QProcess: 1. On linux, when starting a new QProcess, the whole callee's application is being forked. The bigger the application is, the longer the fork takes place. And QtCreator is a really huge. So, QtcProcess comes with a solution: all the processes are being started not directly by QtCreator, but with helper application called qtcreator_processlauncher. All start requests of all QtcProcesses are redirected to that application. Since qtcreator_processlauncher is much smaller that QtCreator, processes start faster. You may turn off this by behaviour by launching Creator with QTC_USE_QPROCESS=true variable set - in this case the process launcher won't be used, but QProcess directly. You may also hardcode the underlaying implementation for your particular instance of QtcProcess by calling QtcProcess::setProcessImpl(ProcessImpl::QProcess). 2. When using QtcProcess it is also safe to destruct it while underlaying QProcess is still being run. QtcProcess takes care about safe termination through Utils::ProcessReaper in the background. 3. There are much more advantages over bare QProcess, e.g. it enables running applications on remote devices transparently. All you need to do is to specify the remote FilePath to your executable inside QtcProcess::setCommandLine() and that's all. I hope this helps Regards Jarek From: Qt-creator on behalf of Knut Petter Svendsen via Qt-creator Sent: Wednesday, January 25, 2023 4:22 PM To: Qt-creator@qt-project.org Subject: [Qt-creator] Utils::QtcProcess What's the idea with Utils::QtcProcess? Why does QtCreator use QtcProcess over simply using QProcess? Also, when trying to debug a ClearCasePlugin which I haven't tested since QtC 4.xx I'm having a hard time actually finding out where the command is actually executed. I'm having problems with stepping in the code to find out why the plugin is failing in my environment. In my own plugin I use QProcess and it works - is there any reason I should start using the more complicated QtcProcess (which I'm having problems with in ClearCasePlugin...) Knut ___ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
