Construct 3 NW.js desktop app [Deprecated]

Post reply

❤Follow Topic(161)

5 favourites

428 posts
- 1
- ...
- 14
- 15
- 16
- 17
- 18
- ...
- 29

From the Asset Store

Telegram Mini Apps SDK

$15 USD

Easily integrate Telegram Mini Apps SDK into your Construct 3 projects for building interactive apps and games.

lostinmind.

- bilgekaan
- - Joined 29 Dec, 2012
  - 99 topics • 534 posts
- 2
- 29 Jan, 2020
- Quote
Anyone having trouble on Onedrive Cloud too ?

i log-on but when i try to list the files i get this CORB

I have the same error, I've already opened a bug report.

github.com/Scirra/Construct-3-bugs/issues/3606
- LuisCGForte
- - Joined 4 Apr, 2017
  - 6 topics • 70 posts
- 1
- 30 Jan, 2020
- Quote
I have the same error, I've already opened a bug report.

https://github.com/Scirra/Construct-3-bugs/issues/3606#event-2977329312

And something about "CORB" ??

But, how to reproduce ? two laptops work fine, but my desktop not.... wtf ?
- bilgekaan
- - Joined 29 Dec, 2012
  - 99 topics • 534 posts
- 2
- 30 Jan, 2020
- Quote
> I have the same error, I've already opened a bug report.

>

> github.com/Scirra/Construct-3-bugs/issues/3606

And something about "CORB" ??

But, how to reproduce ? two laptops work fine, but my desktop not.... wtf ?

Idk:D Browser works fine.

Maybe the reason is this part: "Error while parsing the 'sandbox' attribute: 'allow-storage-access-by-user-activation' is an invalid sandbox flag."

When I remove the c3 files from AppData and open a fresh c3 desktop, the only error is the sandbox flag.
- LuisCGForte
- - Joined 4 Apr, 2017
  - 6 topics • 70 posts
- 1
- 30 Jan, 2020
- Quote
Maybe the reason is this part: "Error while parsing the 'sandbox' attribute: 'allow-storage-access-by-user-activation' is an invalid sandbox flag."

When I remove the c3 files from AppData and open a fresh c3 desktop, the only error is the sandbox flag.

I downloaded the NW.js and extracted all contents inside C3 Desktop an replaced all files, C3 works now and i can access my cloud files without any error, but cant debug, cant go fullscreen etc.....

i think the NW.JS provided is outdated....
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- LuisCGForte
- - Joined 4 Apr, 2017
  - 6 topics • 70 posts
- 1
- 30 Jan, 2020
- Quote
> Maybe the reason is this part: "Error while parsing the 'sandbox' attribute: 'allow-storage-access-by-user-activation' is an invalid sandbox flag."

>

> When I remove the c3 files from AppData and open a fresh c3 desktop, the only error is the sandbox flag.

I downloaded the NW.js and extracted all contents inside C3 Desktop an replaced all files, C3 works now and i can access my cloud files without any error, but cant debug, cant go fullscreen etc.....

i think the NW.JS provided is outdated....

i downloaded a fresh NW.JS and put package.json inside his folder, but problem still...
- bilgekaan
- - Joined 29 Dec, 2012
  - 99 topics • 534 posts
- 1
- 31 Jan, 2020
- Quote
i downloaded a fresh NW.JS and put package.json inside his folder, but problem still...

I tried version c78, cloud works fine but preview has issues.
- LuisCGForte
- - Joined 4 Apr, 2017
  - 6 topics • 70 posts
- 1
- 31 Jan, 2020
- Quote
> i downloaded a fresh NW.JS and put package.json inside his folder, but problem still...

I tried version c78, cloud works fine but preview has issues.

Someone as fixed that the CORB, i woke up now and clicked on Cloud it opens fine without any edit...

Preview as no issues for now

Only cant debug in popup or dialog, i need to remote preview to debug, also C3 doenst open F12 too

Scirra are not friendy of CORS/CORBs 😂
- LuisCGForte
- - Joined 4 Apr, 2017
  - 6 topics • 70 posts
- 2
- 31 Jan, 2020
- Quote
well, seems to problem solved..

its just NW.JS "SDK" version

Normal version of nw.js only for produce and the sdk... well.... for C3 of coarse...

Maybe put this info on the first post, if someone have less knowledge on nw.js like me this will save time.
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,331 posts
- 2
- 5 Feb, 2020
- Quote
Updated the original post with new downloads based on Chrome 80 (NW.js 0.44.0).

Note: in future the distribution of NW.js releases will change. See this forum post for an outline of planned changes.
- newt
- - Joined 12 Nov, 2008
  - 396 topics • 10,741 posts
- 1
- 5 Feb, 2020
- Quote
Fyi the current version previewing isn't quite as smooth as using the web version with the Nwjs download remote preview.
- TheRealDannyyy
- - Joined 30 Sep, 2014
  - 95 topics • 1,192 posts
- 1
- 6 Feb, 2020
- Quote
I'd like to ask one more question regarding NWjs editor support after retirement. Will we still be able to report NWjs specific editor bugs or will those not be looked into anymore?
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,331 posts
- 2
- 6 Feb, 2020
- Quote
I suppose we will have to investigate NW.js bug reports if people rely on it for features like NW.js debugging. However if there isn't much NW.js specific code, hopefully those cases will be rare.
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,331 posts
- 1
- 9 Apr, 2020
- Quote
I've updated the original post with the new approach to releases as I outlined in January. This means you can now download your own NW.js versions to use with Construct 3, allowing NW.js updates to happen without our involvement. It also means for the first time you can choose NW.js platforms other than Windows 64-bit, such as Windows 32-bit, Mac and Linux. Note however that no testing has been done with the editor the NW.js versions of Mac or Linux, so I can't guarantee how that will work. However NW.js has good cross-platform portability so in theory it should work the same as on Windows.

Hopefully this new approach works out smoothly; let me know if anything seems wrong.

Note NW.js 0.45.0 based on Chromium 81 came out this week, so to update to that version, use the new approach. New NW.js versions, including beta and patch releases, are announced on the NW.js blog and on their @nw_js Twitter account.
- TheRealDannyyy
- - Joined 30 Sep, 2014
  - 95 topics • 1,192 posts
- 2
- 9 Apr, 2020
- Quote
I've noticed that the official NWjs releases provided by Scirra, are a lot less bloated than the stuff that comes from NWjs.io. This goes not just for C3 desktop but for NWjs exporting in general.

Just wanted to ask if you guys have any self made "de-bloating" software/script or similar, that you could perhaps share with us? Unless it's being done manually of course.
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,331 posts
- 4
- 10 Apr, 2020
- Quote
I manually removed a few files from our releases that aren't needed for the purposes of Construct, including:
- pnacl (Portable Native Client), a browser plugin that Construct doesn't use (and Chrome will remove themselves in future anyway), including the .nexe file
- All locales other than en-US
- The tools chromedriver, nwjs, payload (these are separate to dev tools and aren't generally needed in Construct)
I did ask the NW.js developers for info about which files are essential, but they said to just use trial and error, and I've noticed the set of files changes sometimes between releases too. So basically you can find out which files are essential by deleting them and seeing if the app still starts! I'd watch out though since some files may be optional and could break features. For example the app may still start if you delete notification_helper, but then it seems likely notifications won't work any more. So it's worth doing a little research to try and figure out what the purpose of the file actually is, and if it doesn't sound important and the app starts without it then it can be removed.