NW.js export update?

  • Morning all - I've just read the blog post about NW.js in construct 3 getting updated, particularly to fix the Mac permissions problem. That's great news - as a C2 user, it's an impending problem I've been trying to figure a way around.

    Does anyone know if this is coming to Construct 2?

  • Any insight would be super helpful. I'll be doing a lot of beta testing soon and the C2 nw.js mac permission workarounds posted aren't working for me, so I won't be able to beta test on osx.

    Thanks in advance

  • Could Ashley or Tom give an update here? Will C2 get the same NW.js export update?

  • Don't count on it. C2 is basically on dying period now. Nothing good from C3 won't come into C2. You probably will have to live with C2 bugs and unfinished (as always) features or buy C3 subscription.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Construct 2 is still going to be actively maintained, but mainly for bug fixes and maintenance. In general, any new features or major changes will only be made in Construct 3.

  • Construct 2 is still going to be actively maintained, but mainly for bug fixes and maintenance. In general, any new features or major changes will only be made in Construct 3.

    Hey, thanks for the reply! 

    I think I understand — the Mac export problem doesn't fall under maintenance, so won't be addressed.

    Not a criticism, but C2 is advertised as being able to publish to Mac, and it's part of the reason I bought it. But I just can't get Mac NW.js working with the currently prescribed method. And in turn, I can't bring my game to that platform.

    So if there's any way to get NW.js -> Mac on the to-do list for C2, it'd be really helpful. Or some kind of step-by-step tutorial for the "open on windows" permissions workaround — it's entirely possible I'm just not doing it right.

    Appreciate your thoughts on this!

  • > Construct 2 is still going to be actively maintained, but mainly for bug fixes and maintenance. In general, any new features or major changes will only be made in Construct 3.

    >

    Hey, thanks for the reply! 

    I think I understand — the Mac export problem doesn't fall under maintenance, so won't be addressed.

    Not a criticism, but C2 is advertised as being able to publish to Mac, and it's part of the reason I bought it. But I just can't get Mac NW.js working with the currently prescribed method. And in turn, I can't bring my game to that platform.

    So if there's any way to get NW.js -> Mac on the to-do list for C2, it'd be really helpful. Or some kind of step-by-step tutorial for the "open on windows" permissions workaround — it's entirely possible I'm just not doing it right.

    Appreciate your thoughts on this!

    Have you visited this thread ?, maybe there you can find information.

    https://www.scirra.com/forum/updated-02-05-2017-the-big-nw-js-roundup-tips-amp-tricks_t184449?&hilit=tips

    I did not know that there is a problem with NW.js for Mac, that is a blow to me because I already have 50% (too much to change engine) of my game and I want it to work on Mac.

    On the other hand I have not investigated that thread and maybe there is some solution, I hope.

  • The workaround in the NW.js export guide works, I've used it several times.

  • "On Mac OS X, there are actually several files inside the app package that need to be executable. The easiest way to preserve the permissions is to copy the exported project using OS X instead of Windows."

    For people who don't have that option, Is there a list somewhere of the files that need to have their permissions set?

  • So yeah if you wanna get the complete version of features advertised for C2 you should buy C3.

  • So yeah if you wanna get the complete version of features advertised for C2 you should buy C3.

    That's not true. Besides this whole issue is to do with how different OSs interpret file attributes. It's not anything specific to C2/HTML5/NWjs.

  • > So yeah if you wanna get the complete version of features advertised for C2 you should buy C3.

    >

    That's not true. Besides this whole issue is to do with how different OSs interpret file attributes. It's not anything specific to C2/HTML5/NWjs.

    True, but I do see what he means.

    If this issue isn't specific to C2, and a fix has been implemented in C3, then why not apply that fix to C2?

    Particularly when the alternative is that an advertised feature is really a bug with a workaround, which requires networking two different machines and operating systems to perform.

  • Everyone wants everything backported to C2. It's just not possible or commercially sensible.

    It's not so much a bug than the design of today's major commercial operating systems. So it's not a bug fix, just a better adaptation to cross-platform support.

  • >

    > > So yeah if you wanna get the complete version of features advertised for C2 you should buy C3.

    > >

    > That's not true. Besides this whole issue is to do with how different OSs interpret file attributes. It's not anything specific to C2/HTML5/NWjs.

    >

    True, but I do see what he means.

    If this issue isn't specific to C2, and a fix has been implemented in C3, then why not apply that fix to C2?

    Particularly when the alternative is that an advertised feature is really a bug with a workaround, which requires networking two different machines and operating systems to perform.

    You can try port the exporter from C3 to C2.

  • Everyone wants everything backported to C2. It's just not possible or commercially sensible.

    It's not so much a bug than the design of today's major commercial operating systems. So it's not a bug fix, just a better adaptation to cross-platform support.

    While I understand there's a (naturally) large demand for all the C3 features to come to C2, it must be frustrating for your team. But I think it's a shame that a request like this is lumped in with all that.

    Exporting easily to OSX isn't a cool feature like an array editor – it's a necessary, promised function of this game engine. So I still struggle to understand why this kind of function wouldn't be considered engine maintenance in C2.

    Or, if it's still not going to brought to C2 users, a step-by-step guide for basic users would be super helpful. And, as Prominent said, a way to do it for those who don't have the option outlined in the work around.

    Thanks for your input in all this

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)