Tools we used to create a hit HTML5 game on Steam

Re:Tools we used to create a hit HTML5 game on Steam by pier25 on Tuesday November 19, 2019 @02:54PM (#21577490)

QT is expensive for the indie developers.

A better choice would have been to simply use WKWebView in macOS and the equivalent in .NET/UWP for Windows.

[ Parent | on HN ]

Re:Tools we used to create a hit HTML5 game on Steam by snazz on Tuesday November 19, 2019 @04:23PM (#21578464)

Except for then you have to deal with whatever version of embedded Internet Explorer .NET uses. Maybe the UWP solution uses Edge now, but that still isn’t wonderful compared with embedding Chromium.

[ Parent | on HN ]

Re:Tools we used to create a hit HTML5 game on Steam by tenryuu on Wednesday November 20, 2019 @02:55AM (#21581952)

Usually in .NET you typically get IE, not Edge. People have been using CefSharp as a replacement. A number of software I have contributed to have done this.

In contrast, UWP applications do use the Edge rendering engine, and while it may or may not be possible to use CEF in these applications, you won't be able to get it certified by Microsoft, therefore no one, at least to my research, has bothered doing so.

I wonder what the future brings with Edge now just being chromium based

[ Parent | on HN ]

Re:Tools we used to create a hit HTML5 game on Steam by colejohnson66 on Tuesday November 19, 2019 @06:38PM (#21579587)

Nitpick: QT isn’t expensive if you agree to the LGPL. If you want to do your own thing, you have to pay up.

[ Parent | on HN ]