Nw.js: Changing process names from "nwjs" and "nwjs Helper" to [Insert Name Here] and [Insert Name Here] Helper

[imjoshdean]

So I have this project I've been working on for a while, but I've been having trouble trying to figure out how to brand name the process without having to recompile nw.js outright (which is what we currently do).

Is there an easy way to do this that I am just somehow missing? How does, say, Spotify do it?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[imjoshdean]

Bump.

@rogerwang? Anyone?

[baconbrad]

Spotify doesn't use nw.js. They created their own shell using the Chromium Embedded Framework.

[rogerwang]

@imjoshdean changing 'product_name' in chrome/chrome_dll.gypi and chrome/chrome_exe.gypi, 'mac_product_name' in build/common.gypi should be good enough.

Please try it and then we'll put it into docs.

[imjoshdean]

@baconface - thanks for the clarification @rogerwang I'll give that a shot.

[rishu-kumar-88]

@rogerwang We are working to change product name from nw.exe to [app name].exe by updating the 'product_name' in chrome/chrome_dll.gypi and chrome/chrome_exe.gypi, but it create nw.exe and executable is not displaying any window. Please let us know any possible solution.

[rogerwang]

@rishu-kumar-88 you'll also search for 'chrome.exe' and 'chrome.dll' in those files and replace them with the name with nw. Also check the file:
chrome/installer/util/util_constants.cc

[Rishu]

@rogerwang We are able to build the executable, but we are unable to launch it. Here is the debug log below:

[0523/202130:ERROR:process_info.cc(608)] range at 0xfe796000, size 0x230 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe79f000, size 0xf84 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe79b000, size 0xf84 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe795000, size 0xf84 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe66f000, size 0xf84 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe66c000, size 0xf84 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe669000, size 0xf84 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe666000, size 0xf84 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe663000, size 0xf84 fully unreadable
[0523/202130:ERROR:process_info.cc(608)] range at 0xfe660000, size 0xf84 fully unreadable

Please let me know any workaround to fix this issue.

[RohitSharma27]

@rogerwang any update on this issue...

[rogerwang]

There should be something missing on @Rish's side. We'll put an official document on how to rename the executable. Thanks.

[rish]

@rogerwang I guess you mean @Rishu not me. 😄

[Rishu]

@Rish Yes, this is for me. @rogerwang Thanks for your update about documentation of rename the executable. Are there any expected timeline for this documentation availability?

[AndryBray]

@rogerwang any way to allow us to setup this with a properties file? or even inside package.json?
are we constrained to build / compile a custom build to get a custom process name?

[Sytten]

I agree, it should be easy to change the process name as it was before...

[tlacaelelrl]

for windows use resource hacker and edit the version info

[AndryBray]

@rogerwang any plan about this feature on 0.15 roadmap?

[gpetrov]

@rogerwang any news on this? Rename of the main nwjs process is easily done, but renaming of the nwjs Helper process seems impossible as everything crashes on OSX afterwards.

[kierans]

I also find it interesting that the documentation tells me to rename nwjs Helper but not nwjs? Oversight?

[IssueHuntBot]

@boostio funded this issue with $30. Visit this issue on Issuehunt