Qt Creator is a fantastic editor and IDE. If you're doing cross-platform GUI development, Qt is a good choice (especially compared to something grotesque and unseemly like Electron), and for Qt development, Qt Creator is as good as it gets. But it turns out that it works really well for generic C and C++ development too, even with obscure C like the Linux kernel, thanks to the Clang code model. I use Qt Creator sometimes when working on WireGuard (in addition to the usual typical vim/cli flow).
Yep, if you can even compare Electron to Qt. Electron is just a buggy ill-conceived hack to wrap a browser with nodejs to make webpages. All it provides is a blank window with no customisation and a huge size and memory overhead.
I hate the slowness and bloat and entire ideology behind electron, BUT...electron apps do a pretty decent job of feeling native on the platform. Something I've never seen a Qt app do.
Would love a counter-example, if you've got one. I'm on a mac.
I can't think of a Qt app that looked odd on macOS. I've developed quite a few pieces of software in Qt for the mac, and they all perfectly use the OS's styles and colors.
I feel like slack is decent. It definitely feels like a webpage, but the embedded UI elements are good -- the text boxes support all the MacOS shortcuts, you can insert special characters using the character viewer, text selection works properly, the menus aren't weird.
I guess maybe I'm just so used to web stuff now that that codes as "native enough" to me?
I've never heard of Figma, but the reason VSCode is as good as it is now is because it's has had increasing parts of it being re-written in C or C++ along with other extensive performance modifications to the electron runtime by the vscode team.
> the reason VSCode is as good as it is now is because it's has had increasing parts of it being re-written in C or C++
Is that true? I've heard that said before but I've also heard that's not true. I haven't been able to find anything indicating any parts of it are written in C/C++ either. The GitHub repo for VScode doesn't have any C in it; infact it doesn't have much but JS/TS:
I agree. Afaik the core of the editor logic in VsCode is all typescript.
There are some native parts, like obviously electron. And I think the find-in-files function uses ripgrep, which is written in rust. But that's a far stretch from "increasing parts of it being re-written in C or C++".
These guys continue to do a great job. If you're looking for a nice cross-platform C++ IDE that supports multiple build systems this is it. I'm looking forward to upcoming meson integration (GSoC project IIRC).
Second this. Fakevim in Qt Creator is one of the better Vim emulation implementations. Not perfect, but it's at least 90% of the way there. Probably 100% if you don't use lots of crazy ex commands like I do
Fakevim doesn't support :wqal or even some basic movements and range specifiers. It may be usable but it's hardly an elegant implementation that only misses "crazy ex commands".
TL;DR: Just set up the "Build" toolchain (configuration) in Qt Creator and point Qt Creator at your target (with the correct ssh user login) for when you click "Run" or "Debug".
These two tutorials use slightly different setups, so don't get confused on details, but both are great to glean tips from.
I've successfully used Qt Creator on both a Linux VM (desktop Intel) and a Windows desktop to build originally-desktop-based Qt projects for embedded Linux on ARM. The projects are not headless, but also do not use X to run the Qt GUI. Instead they use EGLFS.
Even if your software doesn't have a GUI, you can still do remote debugging with Qt Creator... or Eclipse, or Visual Studio , or anything that has the proper hooks.
I don't think any sane developer would want to use a remote X server to get to an instance of an IDE.
As long as you have the proper cross toolchain (some cost $) set up correctly in Qt, and your target code is all included properly (libraries and headers for your target, NOT your dev machine), you should be able to do exactly what you want for any desktop+remote target pair.
Additionally you don't even have to work in Linux to target Embedded Linux:
Specifically, I think the tip to make an exact copy of the target's sysroot structure (libraries, headers, etc) on your dev machine using rsync (and remember to fix the symbolic links!) is very valuable.
Then make sure your project is (only) aware of those headers and libraries.
