Skia VS imgui

Android uses JNI to call native c functions to handle in scaling in pretty much any container derived from View. These C functions are provided by SKIA open source API. The specific function you're looking for is ScalePixels . They say that they use Bicubic in the comments

Flutter is much closer to a "game engine" as it draws it's components using Skia [1] compared to e.g. React Native that creates platform native elements. So you are right, you won't get the underlying platform's widgets. Flutter should act as an intermediary and make this as frictionless as possible though so OS level changes will be propagated or exposed by Flutter or you app directly accesses them but I have no practical experiance in this.

This is not always so cut and dry awful as you might think though. The platform native widgets also have limitations and expectations that might not fit your vision of the app so even fully "native" apps might re-invent the wheel in a couple of places to make things work as they want. Also I've hardly ever come accross an application that works by just combining the basic platform widgets and not look and feel pretty basic.

Also cross platform apps not respecting e.g. Zoom, Resolution, Orientation, A11y, etc. is more often than not, just the developer's not implementing the required things. The framework might support all of these use-cases but not fully automatic in some cases.

[1] https://skia.org/

Chrome uses Skia which AFAIK is GPU accelerated. Not sure about the SVG part though.

https://skia.org/

https://en.wikipedia.org/wiki/Skia_Graphics_Engine

I took a look at using Skia, but the C bindings are marked as not stable and it does not look like an easy to distribute library (plus compiling it takes a long time).

https://skia.org/ is the 2D Graphics library which is used by Chrome/Firefox/Flutter/Android

https://skia.org/ This is used by the sublime editor, so I think it'll match your use-case.

You could look into Skia (BSD), it's used in Chrome, Flutter, Firefox and I think LibreOffice also uses it for some platforms. The other big alternative I'm aware of is Cairo (LGPL).

I've been creating my own environment for generative art using SkiaSharp, which is a C# wrapper around the Skia 2D graphics library (https://skia.org).

Most browsers use Skia, an open source c++ 2d library

There are plenty of other GUI libraries out there, and the most common and ubiquitous ones all have extensive documentation, tutorials, or at least examples. Something like Dear ImGui kind of expects you to know GUI programming already, they cater to a more advanced GUI developer.

Besides 3D programming work you are also welcome to improve upon tools like our installer, or help with the UX design of Reshade. We use Dear ImGui. The documentation could probably also need more work.

Off topic -> but on topic of the original post. Do you know if https://github.com/ocornut/imgui is available for embedded? It might be too much but it for a reasonably capable system it's better than web or some high powered UI like Qt.

> I loved the fact Qt had it's own standard library, I know some c++ purists won't like that and the qmake , but we need to understand how many platforms Qt targeted and that the col new C++ features were not there on all this platforms when Qt4 was created

Indeed so! Qt is living today with the fact that it was built and designed long before C++11 was really a thing (where C++11 is the baseline of modern C++ and I would argue that even C++17 should be considered the baseline). The design decisions of Qt are directly against modern C++ design. I think that's ultimately the core of the problem: that modern Qt is orthogonal, not complementary, to modern C++.

Range-for loop? Oops, accidentally detached and deep-copied into a temporary.

Move objects? Just, no.

unique_ptr? Nah, QScopedPointer. Also still not moveable. make_unique? Nah, reset(new...) and ignore the modern advice that you shouldn't use `new`

Qt still takes naked pointers and decides willy-nilly whether to take ownership. It still has examples everywhere for using naked new without even mentioning the context of a smart pointer. It has the concept of "you used new, but the parent actually owns it, unless the parent is null" which is just a time bomb for anyone new to the framework let alone the language.

No, there's no way I would recommend Qt to someone who isn't experienced. Since I wouldn't recommend it then it's no wonder to me why Qt isn't used so much. It has little to do with C++ and a lot more to do with the design decisions of Qt itself.

> IMO the reason Qt is not used as much is because it uses C++

Arguably. Also arguably is because Qt brings along a lot of unnecessary baggage. You mentioned using Qt requires using qmake (which definitely counts as arcane, if not archaic); cmake does a pretty good job of wrapping qmake but doesn't eliminate it. And all of that is because of Qt's non-standard magical signals & slots system which is really just a more error-prone semi-async system when compared to any other eventing system.

Using Qt efficiently strongly needs Qt Creator which isn't nearly as good as Visual Studio or VS Code and not as feature-rich as CLion or other intellij-based IDEs I've used -- but at least it performans way better than CLion or intellij trash.

Qt's license changing in 5.15 has also become a significant penalty to non-commercial use. This fact alone means there's no way I'd use Qt in a new project, even a commercial one.

Modern Qt developers also have to become javascript developers since Qt's UI is heavily driving towards QML. That's an unfortunate direction and also inhibits adoption of Qt IMO. Why write an application in C++ if you need to learn javascript anyway? There are better feature-rich javascript frameworks with better community adoption and better price points.

> what would you use today if you need to make an application for someone, something simple like some buttons, menus and it does a bit of work maybe with some files or the internet), the goal is to be fast and have very few bugs that you will have to support by fixing them

For GUI, Dear Imgui [0].

For network, Asio [1].

For files, plain standard streams. They're not fast but if your files are your bottleneck then I'd consider memory-mapped files.

[0]: https://github.com/ocornut/imgui

[1]: https://www.boost.org/doc/libs/1_77_0/doc/html/boost_asio/re...

ImGui has a docking branch.

Have you tried using a dear imgui template for your tech stack? example_glfw_opengl3 should get you running.

If you want to make a gui program using C++, you could try using DearIMGUI. https://github.com/ocornut/imgui

There are many options but I believe the most popular paradigm is to use immediate mode UIs, like Dear ImGui, and hook them into the rendering engine itself (i.e. translating the UI draw calls to DirectX / Vulkan), with custom textures/fonts/etc. to make the UI feel 'native' to the game.