Allow compiled V8 binary as application entry-point.

To protect sources, they are compiled with V8 and then executed using evalNWBin on a Window. In order to execute this however, you need to specify either a HTML or JS entry-point in package.json which then loads the compiled binary.

It would be beneficial to reduce the needed route here if we could simply specify a compiled V8 binary as the entry-point.

{
	"main": "source.bin"
}

I am not familiar with the internals of nwjs, so I am unsure if a Window context is specifically required before hand. If this is the case, then simply spawning a blank window without any HTML using window sub-fields defined in the package.json should be fine, which the user can then obtain with nw.Window.get() or such.

Overall, it would be nice to reduce the need for having to include a index.html which just contains <script>nw.Window.get().evalNWBin(frame, 'binary.bin');</script> when all bootstrapping is done in the compiled script.

[NbrTDB]

Yeah it would be much tidier to be able to specify a binary directly in package.json. I feel like it’s worthwhile just for the convenience, if nothing else.

[rogerwang]

It would be the same as pointing main to a JS file with a single line of calling evalNWBin. So it could be done in the application…