Removing NaCl build flavor

302 views
Skip to first unread message

Roger Wang

unread,
Apr 17, 2016, 10:53:21 PM4/17/16
to nwjs-g...@googlegroups.com
Hello,

We are considering removing the NaCl build flavor because the percentage of it is very low in download stats. After the removal the NaCl feature will still be supported in the SDK build.

Please give your comments.

Thanks,
Roger

lza...@gmail.com

unread,
Apr 17, 2016, 11:16:38 PM4/17/16
to Roger Wang, nwjs-g...@googlegroups.com
+1 for removing it


Laszlo
--
You received this message because you are subscribed to the Google Groups "nw.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-general...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

alex...@gmail.com

unread,
Apr 18, 2016, 3:02:34 AM4/18/16
to nw.js
Hello,

As I see NaCL it's feature give us ability to connect and use custom c++ binding libraries to extend browser functionality, like internal PDF, extending JavaScript factory and etc. Like ActiveX in Microsoft IE.

I have 2 questions:
1. Why this feature is not a part of normal flavor?
2. Your decidion is just based on downloads rate, really?

Roger

unread,
Apr 18, 2016, 4:54:37 AM4/18/16
to alex...@gmail.com, nw.js
Hello,

1. Normal build tries to provide full HTML5 features while remains the minimal size for it. So NaCl build is not in it. It is for developers who don't want the NaCl feature.
2. Is this a question?

Roger

--

Ashley Gullen

unread,
Apr 18, 2016, 7:15:40 AM4/18/16
to Roger Wang, nwjs-g...@googlegroups.com
For Construct 2 we use pure HTML5 code so have no need for NaCl stuff. I suspect many NWjs users are similar, explaining the download difference.

However what we really want is a SDK-without-NaCl build. We need to ship support for dev tools, but don't care about NaCl. So I generally just download the SDK build and delete away the NaCl files. It seems to work... but an official build like that would be useful I think.



--

jon.w....@gmail.com

unread,
Apr 19, 2016, 12:12:48 AM4/19/16
to nw.js, ro...@nwjs.io
I also want SDK-without-NaCl.

armo...@gmail.com

unread,
May 11, 2016, 7:39:19 AM5/11/16
to nw.js, ro...@nwjs.io
Dear Roger and all,
I just found this thread.

Unlike other people here, I really need the NACL support. The reason is, some Chrome apps (not developed by me) use it and I run those apps in a standalone way with nwjs (example: Citrix chrome app).
So removing the support is catastrophic for me because those apps won't run anymore! Running the SDK build is not an option because my users should not access the source code of an application in production.

I can understand you want to lower the size of the runtime but consider that a specific build will always find a user needing it.

Let me propose something: if you keep NACL in SDK build, it would fit my need if we can disable (with a command line flag for example) the debugger activation from right-click menu. Maybe it could be a good compromise for everybody?

Best regards

Roger Wang

unread,
May 11, 2016, 9:28:06 AM5/11/16
to nw.js, ro...@nwjs.io, armo...@gmail.com
I can see to add a command line argument to disable showing devtools. Please file an issue to track it.

Roger

armo...@gmail.com

unread,
May 11, 2016, 9:42:40 AM5/11/16
to nw.js, ro...@nwjs.io, armo...@gmail.com
Ok, I'll do it right away.
Thanks a lot.

ulf...@gmail.com

unread,
May 12, 2016, 1:17:52 PM5/12/16
to nw.js, ro...@nwjs.io

Wait what?! I know I'm seeing this pretty late but I rely heavily on the NaCl support, which has been working nicely btw., for a commercial video streaming application I'm developing for a local telco. I need NaCl because that is the best video player option available to me.

Please consider keeping the NaCl flavour.

Ulfur

Alexander

unread,
May 12, 2016, 1:23:37 PM5/12/16
to nwjs-g...@googlegroups.com

Maybe you can still build NaCL build from sources


12.05.2016 20:17, ulf...@gmail.com пишет:
--
You received this message because you are subscribed to a topic in the Google Groups "nw.js" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/nwjs-general/uyNwqEPowd0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to nwjs-general...@googlegroups.com.

armo...@gmail.com

unread,
May 12, 2016, 1:46:25 PM5/12/16
to nw.js
Using a product and compiling it are really different things. I tried to build once, it's really not for me and I thank Roger and other team guys for doing it for us.
Open source doesn't mean simplicity and from my own experience, building from source is complicated, long, painful, especially when you don't have knowledge, a good working environment, time and free disk space! Other experienced people with the good development environment do that better and quicker than us...
Brgds

Úlfur Kristjánsson

unread,
May 13, 2016, 10:57:29 AM5/13/16
to armo...@gmail.com, nw.js
Yeah, that's pretty much it. I probably could build my own NaCl flavour if I had the time to dive into the project code. However, as the application has a fairly complicated build procedure already I am reluctant to add further steps to it and even if I wanted to I really don't have the time for it.

For now I will continue to use the 13.0 beta build I am currently using, meanwhile I will investigate if I have any feasible alternative options.

Pedro Lucas da Silva Junior

unread,
May 13, 2016, 12:20:06 PM5/13/16
to Úlfur Kristjánsson, armo...@gmail.com, nw.js
Build nw.js is easier than you think. See: http://docs.nwjs.io/en/latest/For%20Developers/Building%20NW.js/

But you need to have a great machine to do it fast (SSD and a good processor).

--
You received this message because you are subscribed to the Google Groups "nw.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-general...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages