geo8bit / nodebob Goto Github PK

Possible features:

• app name
• app ico path
• debug/release mode
• which .dll files to add
• keep/discard package file
• store multiple build profiles

After building the app on a fresh Windows VM, opening the app gives a giant warning about the file being unsafe.

Is there some sort of signing required for Windows apps that this build process doesn't support?

I created an nw application (uncompressed), built with nodebob.

This application is installable in the folder chosen by the user.

When the application runs, it does so from the temporary folder.

How simply run the app from the chosen folder, please?

Hi @geo8bit,

I'm a member of NW Utils. I'm trying to consolidate NW tooling so it's easier to find useful projects and give much needed life to stagnant ones.

Hope to chat soon!

Best Regards
Ayush

nodebob does not work if there are spaces in the current directory

In case we have subfolders inside the nodebob/app/ folder, 7z does not store them in app.nw.

i was able to compile the sample app using build.linux.sh. there were two folders created:
release.linux-ia32
release.linux-x64

inside these two directories is the application 'app' which i cannot run:

rationalboss@ubuntu:~/Downloads/nodebob-master/release.linux-ia32$ ./app
./app: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

rationalboss@ubuntu:~/Downloads/nodebob-master/release.linux-ia32$ ./app
./app: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

The typical cmd horror. As soon as there's a space in the cwd everything fails.

Icon does not seem to want to change. Everything is correctly set, in file and with app.ico. However, the icon shows when the application is launched. Stays default otherwise.

I finally achieved how to implement the new node-webkit v0.10.1: (Jul 30, 2014, based off of Node v0.11.13, Chromium 35.0.1916.113).
I didnt change the batch files, actually i dont know anything about the code of it.
Two things has to be done if you want to update the batch (suggestion):

• In every build, copy the necesary files overwritting everything, not just the .exe (in windows), in order to prevent problems between file versions.
• new node-webkit (10.0 or more) need other new files in the release folder.

Consider using:

• ShellJS cat command instead of windows copy
• node-archiver instead of 7z

When testing my node-webkit application by passing the .nw to nw.exe, I can launch as many instances of it as I like. However, after compiling it with nodebob, I can only seem to launch one. Is there any way to prevent this behavior? The application I created is designed to have multiple instances running side-by-side.

Edit: I just manually compiled a .exe (using the instructions here), and I get the same limitation. Sorry, this is probably not a nodebob-specific problem. Feel free to close; I will likely need to look to node-webkit for answers.

Enabling nodebob to get parameters so i could ran
nodebob -app c:\nodeapps\mycoolapp

Anolis Resourcer