If you want a high quality image with a transparent background, select “PNG” from the list. When the Export dialog pops up, enter a name for the file and decide where you’d like to save it. Once the icon you’d like to extract is selected (usually the first, largest one), click File > Export in the menu bar. The largest one will be the first in the list (seen in the pane on the left), and it should be at least 256×256 pixels in size. In the “Preview” app, you will notice that the ICNS file stores icons in multiple sizes. Double-click the “ApplicationIcon.icns” file, and it will open in Preview. Inside the “Resources” folder, you will find a file labeled “ApplicationIcon.icns.” This is a special icon file that contains several different-sized icons for the app. It could prevent the app from running properly in the future. See wiki of NW.js for more tools of packaging your app.By the way, while you’re poking around inside an application package, be sure not to move or delete any files within.
See Support for Mac App Store for details. You should sign your Mac app, or the user won’t launch the app if Gatekeeper is turned on.
* Contents/Versions/n.n.n.n/nwjs Helper.app - rename the directory to ‘foobar Helper.app’ * Contents/Versions/n.n.n.n/nwjs Helper.app/Contents/ist - change CFBundleDisplayName * Contents/Versions/n.n.n.n/nwjs Helper.app/Contents/MacOS/nwjs Helper - rename the file to ‘foobar Helper’ foobar) the helper application will be shown as ‘foobar Helper’. * package.json – add a string field product_string (e.g.
* Contents/Resources/en.lproj/InfoPlist.strings - CFBundleDisplayName * Contents/MacOS/nwjs - rename the file to the value of CFBundleDisplayName To rename the application, the following files should be modified: You can view Implementing Cocoa’s Standard About Panel on how this file will influence your app and what fields you should modify.
On Mac OS X, you need to modify following files to have your own icon and bundle id: To distribute your app through the package management system, like apt, yum, pacman etc, please follow their official documents to create the packages. To create a self-extractable installer script, you can use scripts like shar or makeself. You can use Windows Installer, NSIS or Inno Setup. You can create a installer to deploy all necessary files onto end user’s system.
Icon for nw.exe can be replaced with tools like Resource Hacker, nw-builder and node-winresourcer. For Mac, name it app.nw and put it in nwjs.app/Contents/Resources/. And put it along with NW.js binaries for Windows and Linux.
You can package all the files into a zip file and rename it as package.nw. It’s the recommended way to pack your app. On Mac, put the files of your app into a folder named app.nw in nwjs.app/Contents/Resources/ and done. Or you can put the files of your app in a folder named package.nw in the same folder as nw (or nw.exe). Make sure nw (or nw.exe) is in the same folder as package.json. On Windows and Linux, you can put the files of your app in the same folder of NW.js binaries and then ship them to your users. There two options to pack your app: plain files or zip file. Choose the proper build flavor for your product or build it from source code.Īll files in the downloaded package should be redistributed with your product, except tools in SDK flavor including nwjc, payload and chromedriver. NW.js provided multiple build flavors for different requirements and package size. You have to redistribute NW.js with your app to get your app running. Please build your app in the root directory, like C:\build\, to avoid this issue as much as possible.
This usually happens during installing dependencies with npm install using older version of NPM (<3.0). The length of path used in your app may exceed the maximum length (260 characters) on Windows.