Construct 3 r450

You're viewing a single comment in a conversation. View all the comments
  • 4 Comments

  • Order by
  • Here's an extract regarding NW.JS from a forum post 11 months ago (https://www.construct.net/en/forum/construct-3/general-discussion-7/refocus-export-direction-183136?kws=nw.js)

    Ashley:

    After that (very long term here) I'd want to drop support for NW.js if possible, but that depends on any outstanding compatibility issues. But if our own custom wrappers can do everything NW.js can, and with easier maintenance and better customisability, then I don't think there's any reason to continue supporting NW.js. But anyone using NW.js now shouldn't worry - this is long term speculation, we're going to keep supporting NW.js for a while yet and only switch over if we have new options that cover everything people want.

    Does this mean that there are now 'options that cover everything that people want'?

    If so, it would be useful to have some kind of universal reference table listing the alternative solutions to existing NW.JS functionality.

      • [-] [+]
      • UpvoteUpvote 1 DownvoteDownvote
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • 1 points
      • (2 children)

      I feel we have reached the point where the new export options do enough to make the switch. Even if there are a couple of remaining gaps, NW.js is still supported on the LTS channel for another 18 months, which gives plenty of time to fill in remaining smaller details.

      • Theres definetely downsides to both webview and nw.js.

        nw.js takes up much more preformance, causing some computers to overheat with CPU-Intensive games, while webview doesn't cause that to happen

        On the other hand, some plugins or sprites, when exported with webview, break for no reason at all. The same sprites work both in the editor and in the NW.js export, so it would be nice to either fix that, or keep both exports for, as said, a while longer.

          • [-] [+]
          • UpvoteUpvote 2 DownvoteDownvote
          • Ashley's avatar
          • Ashley
          • Construct Team Founder
          • 2 points
          • (0 children)

          If there is a bug that only happens with an export option like Windows WebView2 that does not happen with NW.js, please file an issue and we'll take a look. We are not currently aware of any such bugs, and both export options are based on the Chromium browser engine, so they should in general have excellent compatibility.