On a global package.json

[Oi Tchau]

I really don't understand how you can change the settings of the node-webkit browser without a global package.json, could someone please elucidate me? For the settings I mean mainly the node-remote allowed sites to run .nw's list.

Here's the original issue I issued:

In node-webkit can you have a global package.json? #1561

I tried readind the docs, specifically https://github.com/rogerwang/node-webkit/wiki/Manifest-format
It says node-remote can allow websites to run node, but it doesn't make sense to have the node-remote option inside of an app, it should be a global thing.

[Roger]

Oi Tchau <affiszervmentio...@gmail.com> writes:

> I really don't understand how you can change the settings of the
> node-webkit browser without a global package.json,

There is no such thing 'node-webkit browser', neither the setting of
it. If you are thinking about an app, then there should be a
package.json.

The official binary is not an application.

btw, there is an issue tracking the requirement of using manifest fields
as command line argument:

https://github.com/rogerwang/node-webkit/issues/281

> could someone please elucidate me? For the settings I mean mainly the
> node-remote allowed sites to run .nw's list.
>
> Here's the original issue I issued:
>
> In node-webkit can you have a global package.json? #1561
> I tried readind the docs, specifically
> https://github.com/rogerwang/node-webkit/wiki/Manifest-format
> It says node-remote can allow websites to run node, but it doesn't make
> sense to have the node-remote option inside of an app, it should be a
> global thing.

--
Roger

[affiszervmention]

Alright, but I really think a design decision should be made as to making it an actual browser (it already functions like one) with extended functionality.

This would get you so many adopters when the apps start flying. (I thought of making a sort of nw app database site, still working on it)