Run multiple apps in one instance of node-webkit

[zcbenz]

Currently we can only run one app per instance of node-webkit now, we should be able to open multiple apps in one instance, e.g. only one browser process and multiple renderer processes for each of the apps, this way we perform more like a special browser.

First we need to refactor the package implementation to make it not global.

Then a new App class should be added which can have multiple Shells and one package, every App should corresponding to a RenderViewHost.

Finally node-webkit should be aware of running instances and decide whether to open a new instance or reuse an existing instance.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[rogerwang]

Is there any motivation or use case behind this? Thanks

On Mon, Oct 1, 2012 at 6:16 PM, Zhao Cheng notifications@github.com wrote:

Currently we can only run one app per instance of node-webkit now, we
should be able to open multiple apps in one instance, e.g. only one browser
process and multiple renderer processes for each of the apps, this way we
perform more like a special browser.

First we need to refactor the package implementation to make it not global.

Then a new App class should be added which can have multiple Shells and
one package, every App should corresponding to a RenderViewHost.

Finally node-webkit should be aware of running instances and decide
whether to open a new instance or reuse an existing instance.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/64.

You may say I am a dreamer, but I am not the only one.

[zcbenz]

It's mainly a Mac issue, on Windows and Linux it's just fine to run multiple instances of node-webkit, but on Mac if you double click a .nw file in Finder, the OS will force reusing the previously opened instance, since we can only open open one app with one instance of node-webkit, we can not start a new app when we've already opened one.

However if users distribute node-webkit themselves or open node-webkit in terminal, they're completely not affected. So this is not a high priority todo.