-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing process names from "nwjs" and "nwjs Helper" to [Insert Name Here] and [Insert Name Here] Helper #4293
Comments
Bump. @rogerwang? Anyone? |
Spotify doesn't use nw.js. They created their own shell using the Chromium Embedded Framework. |
@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. |
@baconface - thanks for the clarification @rogerwang I'll give that a shot. |
@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. |
@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: |
@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 Please let me know any workaround to fix this issue. |
@rogerwang any update on this issue... |
There should be something missing on @rish's side. We'll put an official document on how to rename the executable. Thanks. |
@rogerwang I guess you mean @Rishu not me. 😄 |
@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? |
@rogerwang any way to allow us to setup this with a properties file? or even inside package.json? |
I agree, it should be easy to change the process name as it was before... |
for windows use resource hacker and edit the version info |
@rogerwang any plan about this feature on 0.15 roadmap? |
@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. |
Fix nwutils#196 Fix nwutils#315 See - nwjs/nw.js#5809 - nwjs/nw.js#5807 - nwjs/nw.js#4293 - nwjs/nw.js#2160 - nwjs/nw.js#5829 Allows you to edit the version string of the resultant Windows executable. These can be easily viewed in Properties -> Details, http://i.imgur.com/oqyRwaa.png Fix issue where the process showed up as `nwjs` in Windows. Now defaults to the `options.appName`
Fix #196 Fix #315 See - nwjs/nw.js#5809 - nwjs/nw.js#5807 - nwjs/nw.js#4293 - nwjs/nw.js#2160 - nwjs/nw.js#5829 Allows you to edit the version string of the resultant Windows executable. These can be easily viewed in Properties -> Details, http://i.imgur.com/oqyRwaa.png Fix issue where the process showed up as `nwjs` in Windows. Now defaults to the `options.appName`
I also find it interesting that the documentation tells me to rename |
If we're going to update the Helper app binary, why not the main app binary? This relates to nwjs#4293
@BoostIO funded this issue with $30. Visit this issue on Issuehunt |
If we're going to update the Helper app binary, why not the main app binary? This relates to #4293
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.
The text was updated successfully, but these errors were encountered: