On 2023-03-01 21:41, Cristian Adam via Qt-creator wrote:
Hi,
As a C++ developer you could actually fix something in Qt Creator. If
it's something minor you can simply fork qt-creator on github, push to
your fork and you'll get binaries created by GitHub Actions.
There are not so many C++ IDEs written in C++, open source, and
cross-platform!
This was important for me before joining the Qt Creator team and
working on Qt Creator itself.
Cheers,
Cristian.
------------------------------------------------------------------------
*From:* Qt-creator <qt-creator-boun...@qt-project.org> on behalf of
Knut Petter Svendsen via Qt-creator <qt-creator@qt-project.org>
*Sent:* Thursday, February 23, 2023 06:38
*To:* qt-creator@qt-project.org <qt-creator@qt-project.org>
*Subject:* [Qt-creator] clangd + qtc vs clangd + any editor
I often get asked by my coworkers why I use qtcreator for general C++
development (non-Qt) when you can use clangd with "any" editor and get
code completion, navigation, refactoring etc. Often they mention vscode
and/or vim.
Assuming that you have a build system in place that can generate a
compile_commands.json file, which advantages does QtCreator give? (non-Qt
c++)
I do have a personal preference for QtCreator, but I would greatly
appreciate it if you could provide me with some insight on the matter.
--
Knut Petter Svendsen
And (as Christian says above) since it's C++ all the way, that means
writing your own custom Qt Creator plugin is easy.
I have one that for example has keyboard macros the inserts texts like
"qDebug() <<", "QStringList" "QByteArray" etc. or the classname you're
currently editing or fancy module headers with the current day and
version no. Such stuff can of course be added to any editor but doing it
using familiar Qt classes saves time for me.
Rgrds Henry
--
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
