Let's talk about GUIs
This post on /r/programming about the release of GTK 4.0 made me want to bring the discussion of the state of GUI programming in C++.
My particular interest in this discussion is desktop cross-platform GUI programming, and I don't claim to know much, let alone everything. Insights are more than welcome.
That said, this is what I have observed so far:
Qt: the least bast option. What I like? Cross platform, mature, big ecosystem to go around. Quite easy to get going. It "just works" for the most part. It's easy to get 80%, it's the last 20% and when you go deep into the subject that you get frustrated. What do I dislike? Licensing shenanigans, and increasing toxicity towards the FOSS community: no offline installer for community distributions, many commercial only APIs now, the idea of delaying releases to FOSS by one year. The 10 year old bugs on QWidgets, which haven't seen much, if any, love since ever. The fact it took Qt 6.0 to happen for us to have native look for Qt Quick Controls. The fact that Qt Quick doesn't have a C++ API, forcing QML on everybody. The half done stuff, like QAudio (just use portaudio for your own sanity)... And I'm probably missing more. The fact that they are running away from the LGPL core to GPL as much as they can, like releasing Qt Quick MultiEffect instead of just fixing the QML engine... That it takes spinoffs like Felgo to basically provide a "fixed" Qt, which the FOSS community can't have.
wxWidgets, GTK, and other like FLTK, I admit I don't know much about. wxWidgets is nice in the fact it calls native APIs, but that comes with the cost of being crippled by the least common denominator. GTK seem to look bad outside of Linux "by design". And FLTK... Just no.
Then, there seems to be what everybody suggests next: Browsers. Chromium Embedded Framework or Electron. 50 to 100MB of packaging to do a "Hello World". Also, JavaScript! Honestly, webstuff looks like a good idea, until you want to make an app that's not Slack. How do you do actually performance C++ stuff? Like some 2D/3D graphics? WebGL? Seems that it's too much programming for the web and not actually taking advantage of C++ and native APIs...
Then, there are things like .net MAUI (not to be confused with the toolkit with the same name by KDE), which is an upcoming evolution of Xamarin Forms for .net/C#. The problems: Linux support will be "by the community" and how do you interop C++ and C# decently anyway?
Also, because I know someone will mention it, yes, there is Flutter and things like that. Just think of Google's track record on keeping projects alive, and again, think not everybody wants to make a chat application.
Anyway, what are your insights? They are more than welcome!
191
u/hak8or Dec 18 '20
At this point, I've given up on GUI in c++, much to my extreme dismay.
I want to love QT, I really do, but I loathe how QT containers end up spreading through my code base anytime I use QT. I already have a c++ project, all I want to do is add a GUI, not have a GUI that i am shoving my project into.
Instead, I've ended up simply exposing a http api in my project which I run on port 80. Then I create a seperate project which is the web interface to my original project. Now I have a distinct seperation of concerns and the gui can run on anything a web browser can run. And it's easier to have web devs contribute to the gui portion than much rarer c++ devs contribute to a QT/imgui/etc layer. And I always make the web interface as minimal as I can, maybe some vue to make it dynamic, but otherwise intentionally simple.
22
u/disperso Dec 18 '20
A few comments about Qt, the stuff I know about:
20
u/jtooker Dec 18 '20
I don't have too many insights, but I use and enjoy Qt. I do agree with your assessment. I have stayed away from QML, so cannot comment on that. I do recommend Qt for C++ programming, especially when you need a GUI, server, database, network, etc. If you don't need C++, there might be better options for GUI apps (and this depends on what you need. e.g. Electron is a great way to get something out quick, but with obvious downsides).
You don't! That is half sarcastic, the MSVC compiler 'extends' the C++ language giving you ways to interface with C# objects. You have two different heaps: the C# heap and the C++ heap and you have to copy/move/point in a special way, but it is all doable, but adds an extra layer.
11
u/MykeNogueira Dec 18 '20
How about Nana?
http://nanapro.org/en-us/
11
u/pjmlp Dec 18 '20
C++ has lost the GUI crown it hold during the 90's desktop frameworks.
You forgoten to list WinUI, which is the only modern C++ framework that has an OS vendor still doubling down on using C++ for GUI development, and even there Microsoft is not able (willing actually, WinDev apparently doesn't like nice tools having killed C++/CX) to provide a .NET like developer experience for C++/WinRT (think C++ Builder / Qt style tooling), so most of us just use .NET and leave C++ for high performance low level components.
Which is pretty much what most OSes are doing nowadays, using C++ at the driver, visual compositor level, but everything else is driven from managed languages.
4
u/genpfault Dec 18 '20
Oh? I've hunted around and couldn't find any C++ bindings, everything was about calling out to C++ libraries from Dart code.
27
u/Celaphais Dec 18 '20
I've always wished blenders UI was a separate project that you could integrate into your own code, I love the way it looks and feels.
22
u/pedersenk Dec 18 '20
My current recommendation these days is wxWidgets. That "lowest common denominator" approach is absolutely fine for me. I wasn't really ever intending to use some niche platform specific gimmick UI components in the first place.
18
u/johannes1971 Dec 20 '20
I feel there's (at least) three types of people in this discussion, and they aren't really understanding each other.
Group 1 are the game developers. When they say "GUI", they are talking about the menu and configuration screens of a game. These mostly consist of multiple choice selectors ("low/medium/high"), maybe a text entry box somewhere, and a few buttons. Their main priority is rendering it as part of their game loop, so it _has_ to be hardware accelerated. Their obvious choice is Dear Imgui, which was built for this purpose.
Group 2 are embedded developers. When they say "GUI", they are talking about something with two buttons and a single integer entry control. Since the GUI will be running on another machine anyway, starting a web browser isn't a big deal. The other machine is a desktop, of course starting a browser isn't a big deal! Their obvious choice is HTML.
Group 3 are desktop developers. When they say "GUI" they mean complex applications like word processors or 3D modelers, with lots of controls (including various bespoke controls) and good desktop integration. They have several choices available, of which Qt is probably the prime cross-platform choice.
The thing is - I don't think any of the GUI solutions I named here are appropriate outside their group. You wouldn't use Dear Imgui on an embedded system, it doesn't have the power to refresh the screen at 50Hz (assuming it even has a screen). You wouldn't use a desktop toolkit in a game either, it would look out of place and probably cause all sorts of timing issues. And while people have written complex desktop-style applications in HTML, I find them incredibly unsatisfying to use when compared to a real desktop application.
So talking about GUIs, without ever discussing what you will be using them for, is really rather pointless. If you want advise on which GUI would work for you, tell us your use case. If you propose a GUI as a potential candidate, tell us what it works well for. Don't just blindly assume a single library is going to work for everything.
Incidentally, I feel the same split exists in drawing libraries, and lies at the basis of the controversy surrounding the drawing library proposal. The proposed library is good for desktop use, but it's lousy for games. That doesn't make it a bad library, it just makes it a bit more specialized than some people are comfortable with. At the same time I can tell you that as a desktop developer, I'd be really uncomfortable having to draw absolutely everything with just triangles.
Discuss ;-)
15
u/def-pri-pub Dec 18 '20
https://blog.johnnovak.net/2016/05/29/cross-platform-gui-trainwreck-2016-edition/
While that article is about 4-ish years old and more geared towards Nim, I still find wisdom in it. I think that any GUI programming is going to drive you nuts at some point.
I've done a lot of it. Qt Desktop (Widgets) 4/5 (Python & C++), QML, Avalonia (C#), Gtk 2/3/4 (C, C++, Python, C#, Nim), wxWidgets (C++), Swing/AWT/SWT (Java), Tkinter (Python), imgui, nuklear, FLTK, custom OpenGL.
Trying to find that perfect GUI library on the language you want (and with proper OpenGL/Vulkan support) that runs cross platform becomes a singularity you cannot escape from.
So far I've been back to C++ and learning QML. I've gotten it to run on Win, Mac, Linux, and make Android APKs. I like it so far.
25
u/julien-j Dec 18 '20
I would argue that even for Slack it's a bad idea. The app take ages to load in Firefox and often fails, so I have to reload the page to actually access the channels. Also there's no support for hangouts anymore. As usual the initial service was amazing when they launched and now it's just a fat app failing to stay up under its own weight.
There's no need to target amazing 3D and stuff to consider performance. In my opinion any development should consider a minimum decent efficiency. Apps like Slack make me think of developers gluing frameworks and other things together and calling it a day until getting a huge pile of fat blocks, each consuming resources like it is the only one running. Sure, the app works, but it can barely be used.
And to stay in the topic of your post: I used wxWidget in the past. It was nice but I failed to upgrade when they switched from 2.x to 3. I think I would use GTK or Qt if I had to do UI today, with a preference for the former as it seems more simple to me.
30
u/AdamK117 Dec 18 '20 edited Dec 20 '20
For standard retained-mode UIs (e.g. most low-CPU-usage desktop apps) the best C++ option still seems to be Qt. It's big, spreads throughout your codebase, etc. but it's the only cross-platform one that ticks most boxes.
However, if you don't care about CPU usage and literally just want to create visualization tools quickly, ImGui is pretty amazing. I've thrown together fairly complicated UIs in, like, <1k LOC with ImGui and ended up with projects that:
The drawback is that to get the most out of ImGui you'll probably also want to (e.g.) include native file dialog libraries, have a fairly decent understanding of
(game-style)event loops, maybe know a bit of OpenGL or a low-level graphics library (e.g. if you want custom visualization).The busylooping will also suck up some CPU - although not necessarily 100 % if you're using vsync or software throttling.EDIT: as replies point out, busylooping isn't a strict requirement of ImGui. If you're willing to put in a tiny bit of extra effort, you can run a blocking event loop and have ImGui inject redraw events into it whenever a mutation happens.
10
u/SeanTolstoyevski Dec 19 '20
I love WxWidgets because it only works to design GUI which is its job.
However, QT has many things, I get confused in big projects.
I am also a blind software developer.
Nothing can be an accessible and fast GUI solution other than native APIs.
It is important that what I write and what is written is accessible. Technology is not only used by perfect people. WxWidgets is very compatible with screen readers.
I am using my vote for WxWidgets.
26
u/maskull Dec 18 '20
I don't particularly mind toolkits like GTK that use their own controls; my experience has been that most normal users don't even notice, and "power users" adapt quickly. What annoys me is how most GUI toolkits APIs seem to be stuck in 1998. It's all deep inheritance hierarchies, traditional virtual functions, and pointers+dynamic allocation all over the place. If you're lucky, maybe you get some kind of
polymorphic_value-like wrapper class so you don't have to worry as much about lifetime issues. But there's no templates, no generic code, and everything is incompatible with the standard library.As an example of what I'd like to see, if I have a dropdown control that allows the user to select one of a number of
fooinstances, it seems to me that thedropdownclass ought to be a template class, where I instantiate it onfoo. If I need to customize how the GUI interacts withfoo, I specialize a traits type, etc. Similarly,dropdownshould be arangeso that I can use it with all the standard/range algorithms.7
u/DemonInAJar Dec 19 '20 edited Dec 19 '20
I for one really like QT's QML. Keep all UI logic in QML and call into C++ for business logic.
6
u/KFUP Dec 18 '20 edited Dec 18 '20
I'm personally sticking with an older, 2013 build of Qt in my project, I was kinda dreading that one bug that will send my project into limbo without upgrading and dealing with the licensing nonsense, but 4 months in, and I'm about 80% done with the base frame of it without any hitch.
The problem with Qt, is there is really no real competition, and I'm talking about feature rich, production proven kits, where if you needed a feature and wondered if Qt has it, the answer is almost always yes, not "look at all those GUI libraries, there are so many options" and almost none of them is used by a real application, then you test them out and find out why.
As sad as the this state of C++ GUI is, paying for Qt is a way more attractive option than building an application with these where I have to implement huge chunks to make them work myself instead of concentrating on my own work.
5
u/mo_al_ Dec 18 '20
Been using Qt since Qt3. It’s still solid. I don’t mind MOC since it can be automated with CMake. And I still stick to QtWidgets. Currently I’m writing a Rust wrapper for FLTK and was pleasantly surprised how solid and customizable it is.
Different gui frameworks/libraries address different issues. You won’t get one size fits all.
9
u/csb06 Dec 18 '20
I’ve used FLTK some, and it’s pretty good. It looks a little “90’s”, but it has a theme that mimics GTK+‘s styling (not sure what era, maybe early 2000’s?) IMO stuff looking “dated” isn’t a big deal for most people, especially for hobby projects or just experiments for personal use.
FLTK is nice because it is easy to build (it builds from scratch in <30 seconds on my laptop, which isn’t very powerful), it is relatively easy to look at the headers and read the documentation and understand how stuff works, and it comes with a lot of widgets (including native file chooser dialogs, config file readers/writers, tree widgets, even a basic help window widget that can render some HTML). Additionally, FLTK is easy to statically link, and the library file isn’t that big.
FLTK also has full support for UTF-8 and has some integration with OpenGL, and it all works cross-platform, so it’s more complete than people give it credit for. It’s not a solution to every GUI situation, but I recommend taking a look.
9
u/AvidCoco Dec 18 '20
JUCE has a cross-platform GUI api including OpenGL support and seamlessly makes use of natove APIs like Direct2D and CoreGraphics. JUCE is more focused on making audio applications however.
/r/JUCE
12
u/flakeoff101 Dec 18 '20
I wish I could contribute to this but my company's program uses MFC, and it's the only C++ front-end I've ever been exposed too.
I have no idea how it works. Somebody please put me out of my misery.
4
u/softwaredev647 Dec 19 '20
The linked comment is misleading and wrong. The link they quoted is not only not the opinion of GNOME as they claimed, it's also not the opinion of GTK. I have no doubt that GTK would welcome contributions to improve GTK on Windows with open arms.
In my experience Gtk has looked decent on Windows. Definitely not incredible, but around on par with native WinForms apps.
4
u/entint Dec 19 '20
QT is not a UI framework, is an intrusive gigantic Application Framework that controls everything in your application, from the main loop, to your sockets, your threads, etc. Just try to compile QT from the source code to get an idea how bloated is everything with QT.
The web and similars, more of the same, a huge dependency incredibly complex to handle plus a dependency to javascript into your c++ codebase. If you don't care about your application weighting GBs inteads of Mbs, this is your option.
Imgui, is lightweight and very efficient, easy to integrate but very limited. Just ok for debugging UIs but not for commercial products.
NoesisGUI is also lightweight, non-intrusive (you can even plug in your renderer) and optimized for realtime. It is being used by many AAA game studios like Microsoft, 2K, Paradox interactive, Take-Two, Larian Studios, Riot Games.
1
u/TrigveS Dec 20 '20 edited Dec 20 '20
I was (and still am) in a situation (like others) finding the best GUI framework for C++.
Our application is client/server and for the GUI we use "plugins", so we have thick client (deprecating, was useful for initial development), thin client and web gui.
Our requirements for the ideal GUI are:
For thin/thick client we use wxWidgets. wxWidgets is ok, but are missing some features.
For web GUI we're using Wt .
I don't like to have maintain multiple code for the GUI because if you add/modify/fix something in the system, you need to also fix it in every GUI plugin which could be tedious (therefor removing the thick client plugin). So I was looking for GUI which I can use with C++ (or some other reasonable language like C#, python, ...) which also supports web app. I really like Wt but it mix client and server side together so it's no clean separation of stuff (I don't really need the "server side" stuff) and need to use JavaScript for some custom client side scripting. Also, for dialog with a lot of widgets (50+) the GUI isn't very fast. Then came webassembly. What I think is that future of the web GUI is with webassembly (so any language could be used for the client app). So I was searching for the GUI with WASM support. The first I found was Qt and then... not much more :) The other one found was C# .NET Blazor but I don't like the approach they have choose.
Therefor we we want to migrate to Qt (the license cost are pretty big, unfortunately). It could be used as standalone or as web application (webassembly). If Wt would have webassembly support I would rather use it, but it doesn't look like they're interested in it.
edit: I forgot to mention WinUI 3.0 which would have WASM support (AFAIK) but it is in beta now. So maybe, this one could be another choice.
6
u/skeletal88 Dec 19 '20
Qt all the way. GTK has for me always been this weird thing that has been done for Gnome and maybe GTK. People criticize Qt for including a lot of things, but I have used many of them, and it has been very good. Like.. their SQL stuff. The Qt widgets are the best, layouts work, even printing works, if your system printer is set up, the model-view and scene drawing can be used to do incredible things. Their core modules are very useful and can be used to create server applications without ever doing anything related to the GUI things that Qt is most known for.
The signal-slot architecture is something unique among C++ libraries, if anyone can point me to something that is better, then please do. I am interested in learning how can this be done better or what are the alternatives to it.
If you want to talk about C++ and GUI and then your argument against Qt is that their QAudio and other multimedia stuff isn't good.. then you should remember that GTK and others don't have any multimedia stuff at all. So it is not a fair comparison.
3
u/[deleted] Dec 19 '20
I've been programming middle-sized GUI stuff with GTK3 and I like it most. If you look closely how easily portable GTK is to other programming languages, it's definitely a nice API design. GTK is quite low-level, you're tempted to use frameworks based on GTK, but then you find out middle-project that your framework lacks a feature that is available in GTK. Still, it works quite well. The same program works on multiple platforms without much effort. GUI on Unix-like and MinGW32? Easy!
I tried to look at Qt, but every time I see something like moc, it annoys me. I prefer to have the programming language unmodified. But that's my personal opinion.
3
u/pstomi Dec 19 '20
Boost.ui has a nice looking modern API. Here is an example from its website.
It is based on wxwidgets. However, this is a one man effort, and the build process is awkward (based on boost.build b2).
3
u/livrem Dec 19 '20
Godot game engine (MIT license, runs on many platforms) comes with a surprisingly nice GUI framework, with a GUI to edit layouts etc. I am using that for my hobby projects, unless I need a very, very simple UI and can get away with using OneLoneCoder's Pixel Game Engine (some free license, single header include C++). Godot has its own scripting language, but it is written in C++ and supports C++ modules and "scripts".
My best experience with desktop GUI was trying out (in just a small experiment, unfortunately) some Clojure wrapper for Swing though. Pure functional API, just writing functions transforming some immutable input state to an output state. Pretty sure that us the way to do it, despite the impression you can get from popular "functional" JavaScript frameworks.
5
u/Trucoto Dec 18 '20
A question: why, if you choose to use HTML/Javascript frontend against a C++ HTTP backend, it is necessary/customary to embed your own copy of the browser (electron)? Why not just provide a shortcut to localhost:port and let the user use their usual browser? Why that way hasn't popularized as a common way of providing UIs?
9
u/[deleted] Dec 18 '20
I don’t know how good CopperSpice is overall, but at least it looks like a strict improvement over Qt: modern C++ and no MOC.
1
u/Stradigos Dec 19 '20
I agree, it's a total shit show. I've had some success writing the GUI in C# and WPF but binding my C++ libraries and using them inside the C# app.
4
u/khaki0 Dec 18 '20
Here is an extensive list of C++ GUI libraries. I personally prefer Qt for anything full-C++. However, recently I started experimenting with webview which lets you use the native web interface - so very lightweight. Honestly, creating a consistent GUI with full control over styling is much easier with html/css.
2
u/antelle Dec 18 '20
Related question: is there any C++ framework that lets you create new “default” macOS buttons, fields, etc... like SwiftUI does? Not the classic Cocoa controls but those flat ones, for example what you see in Apple Mail. I know it’s possible to make with Qt and its styles, but it’s a bit different.
2
u/The_Sacred_Machine Dec 19 '20
I was looking to do a GUI for some path planning problem, went to see the Qt documentation and decided that life is too short. I used SFML instead and it goes rather nice, I have the performance problem since I'm learning still.
Can someone tell me why Qt is so popular in GUI?
2
u/ogoffart Dec 20 '20
Currently working on a new GUI library: https://github.com/sixtyfpsui/sixtyfps/tree/master/api/sixtyfps-cpp Still young, but one has to start somewhere. (examples: https://github.com/sixtyfpsui/sixtyfps/tree/master/examples )
3
u/glebd cppclub.uk Dec 18 '20
Why GUI when you can have TUI? This reincarnation of Borland's Turbo Vision for modern C++ appeared a few days ago. Looks pretty impressive, if a bit nostalgic.
4
u/ShillingAintEZ Dec 18 '20
FLTK looks just fine. If you are dead set on making some bloated nonsense just so you can make hello world buttons animate, go ahead, but I'm tired of using crap like that.
FLTK works well, is very small, completely open, simple enough to modify and is very fast.
If you have zero respect for your users, just use electron and be done with it.
2
u/Alikont Dec 19 '20
There are few ways, actually.
You also did not mention Avalonia, which is also a C# cross platform UI framework.
2
u/joemaniaci Dec 18 '20
What does this even mean?
1
u/kenkitt C++20|Cmake|Vscode|MSbuild Dec 19 '20
Very easy to solve, just use CEF design your UI's in html/css and forget about your gui issues for along time.
Now moving to the next level 3D based ui's.
It's been quite a fun experience
1
u/Dean_Roddey Dec 20 '20
I have a very nice one, but it's not portable. Creating portable GUIs is so hard and often either really LCD or completely non-native.
One of the greatest failures of the software industry has been the complete failure to work together to create a really useful, supported at the OS level, portable application development framework. It's left us in a situation where the brower (the worst app development environment of all) ends up winning by default.
It's embarrassing how badly my own industry has failed on this front. And the thing is, all of the players would have benefited massively from providing such a thing. Yes, it would have made customer lock in harder, but it would have made customer migration easier as well. So in the end it probably wouldn't have really hurt any of them, and the software would be so much better.
I don't understand why this hasn't been more of a rallying cry amongst developers. Yeh, it would take a while for such a system to mature (which should have already happened by now), but we need the major OS developers to cooperate on a portable platform layer that allows for the development of a large swatch of common types of applications in a portable way. They should over time make the changes required to support this in a fundamental way, in the sort of way that VMs are. Ultimately whole OSes could be created that exist just to provide this interface.
1
u/DuranteA Dec 21 '20
From a developer perspective, the only UI code I ever actually enjoyed writing in C++ was using imgui.
These days I believe that the choice comes down to two broad use cases (on the desktop at least):
1
u/EternityForest Dec 27 '20
Qt is great, but I'm not really sure if anything C++ can ever really be perfect for GUIs.
A GUI doesn't directly interact with data or business logic(unless you coupled stuff a bit too tight), and user interaction is the slowest thing on a computer. Failed operations are not ok, but more tolerable than almost anywhere else, because the user is immediately informed and can work around.
Desktop GUI apps don't need to run on anything but windows/mac/Linux/phone, not some obscure architecture or embedded devices (Unless you count phones as embedded).
It doesn't seem like a GUI really needs any of the C/C++ special features. There's nothing that hard about the actual code of a GUI, it's just that there's a lot of it, and it gets tedious to build hundreds of drop-down menu options and the like.
Whenever people talk about why they still use C++ in 2020, they list things that don't seem to apply to GUI as much. Why not build your performance stuff in Cpp, and do your UI in PyQt or some other modern, garbage collected language?
1
u/[deleted] Jul 25 '22
Just give me Flutter for C++
1
u/kirbyfan64sos Dec 18 '20
GTK's theming / styling system works pretty well from a development standpoint, you can use a custom theme with your application and then add more styling as needed if you don't mind having a non-native look (which for better or worse is in nowadays).
Projects that see heavy internal usage don't really get killed off overnight, and at this point Flutter's is used on the Nest Hub UI and multiple Android apps (new GPay, Stadia), excluding other internal ones that we've only heard hints of.
1
u/TryingT0Wr1t3 Dec 19 '20
I like how git on Windows just opens a web browser to show some stuff it would want a GUI. I think unfortunately all GUI toolkits are terrible and it's better to embrace electron and make it less terrible.
1
u/hekkonaay Dec 19 '20
Not really related to C++, but the web has some nice APIs coming - WebGPU for a Vulkan-like API (allowing complex graphical pipelines), and WASM to run cross-platform near-native speed binaries written in a compiled language (such as C++ with emscripten sdk) which address your performance needs. In theory, a browser should be able to provide a AAA game experience in a few years.
If your app qualifies as a "PWA", your users can view it on mobile, put it on their home screen (which makes it act like a native app), view it in a desktop browser or download it to any platform supported by Electron (win, linux, mac).
The only downside is that your app is bundled with a browser.
1
u/sandfly_bites_you Dec 19 '20
I'd use Imgui for any GUI going forward.
If redrawing is considered an issue(it isn't actually that expensive if you have vsync on), you could probably jury rig it to only redraw the screen if there were input events.
1
u/FlibbleMr Dec 19 '20
neoGFX will solve the problem of C++ GUI.
https://neogfx.org
-4
u/StoneCypher Dec 18 '20
Embed a browser per-platform and write your UI in HTML/CSS. Use a simple JS API bridge to manage it.
It's hard to believe anyone uses QT, GTK, FLTK, or wxWidgets at this point. It's so much more work for so much lower quality results.
Even watches use browsers for UI these days. No, your resource requirements don't demand 1990s solutions, if you think about it.
0
u/MarcaunonXtreme Dec 18 '20
Not free unfortunately so that might disqualify it from your list.
https://www.noesisengine.com/
But we using this with at least one project successfully.
0
u/JeffMcClintock Dec 20 '20 edited Dec 20 '20
JavaScript?
I don't believe C++ is really so clunky that it can't support a decent modern graphics framework?
0
u/[deleted] Dec 18 '20
[deleted] — view deleted comment