MonoGame VS Qt

To highlight this shift, we are introducing a new website which is now fully automated with Github. The paint is still fresh, but we hope to expand it with more information about the MonoGame Foundation, like how it operates, and how to join it or contribute.

https://github.com/MonoGame/MonoGame /

Yes, it is possible, but you need to use a game framework not a game engine.

Example of a game framework: http://www.monogame.net.

Monogame, though it doesn't do much hand-holding: https://github.com/MonoGame/MonoGame

Webassembly support is spotty, though in progress AFAICT.

Used by a few 2D games like Stsrdew Valley and Celeste.

Some that I am aware of and that support at least Windows and Android are (Monogame)[https://www.monogame.net/], (Cocos2D)[https://www.cocos.com/en/cocos2d-x], (LÖVE)[https://love2d.org/]. But there are likely many more. Even more basic ones which are just another abstraction layer on top of SDL (like (Oxygine)[https://oxygine.org/]).

- https://www.monogame.net/

Qt mono repo : .. you could check out all submodules and simply use CMake to exactly achieve this. A mono repo also means that if I only use qtbase and declarative, I would need to have all submodules in there? - No

For e.g. if you’re writing a framework, you need to interface with Cocoa on MacOS to draw windows, which only provides an Objective C or Swift interface. You can look at the Qt source code and see how they do it: https://github.com/qt/qtbase/tree/067b53864112c084587fa9a507eb4bde3d50a6e1/src/plugins/platforms/cocoa

That's because Qt 6 wholeheartedly converted to CMake for you. (At least it is better than qmake.) In order to support this Qt has this large battery of CMake files [1]. Qt is of course a clear outlier, but you can't expect the same level of support from every other library you want. My points about "anything exotic" still stand.

[1] https://github.com/qt/qtbase/tree/dev/cmake

What are you talking about? Qt has GTK theme support built-in: https://github.com/qt/qtbase/tree/dev/src/plugins/platformthemes/gtk3

This looks like the Qt bug solved by this commit: https://github.com/qt/qtbase/commit/acaabc9108dfe75530960cf8e3ec4f3602cd82e0

Yeah, I'm sure it's completely unheard of. Oh except that it took me all of a couple minutes to find an example of that exact thing in one of the largest, most commonly used C++ frameworks out there.

I don't see any connect in https://github.com/qt/qtbase/blob/dev/src/corelib/tools/qsharedpointer_impl.h, and QPointer isn't a QObject (though I don't know if the latter is actually necessary for signal-slots). One (unreliable) way to test is to see if a QPointer fails to be nulled out when the QObject is blocked by a QSignalBlocker. Alternatively I'd set a data breakpoint on a QPointer and try it out. But I don't have the time right now.