They're different projects with different goals. Diversity is good!
On Mon, Feb 4, 2013 at 9:32 PM, mgutz wrote:
> I think you're oversimplifying it. For example, in node-webkit if you can
> drag and drop a file into the client area, you get the full path. You're
> basically running a server in
simplicity is good.
On Tue, Feb 5, 2013 at 12:32 AM, mgutz wrote:
> I think you're oversimplifying it. For example, in node-webkit if you can
> drag and drop a file into the client area, you get the full path. You're
> basically running a server in node and running chrome with some permissive
>
I think you're oversimplifying it. For example, in node-webkit if you can
drag and drop a file into the client area, you get the full path. You're
basically running a server in node and running chrome with some permissive
flags set.
On Monday, February 4, 2013 6:14:43 PM UTC-8, hij1nx wrote:
>
The difference is several thousand lines of code -- in fact its about
30 lines of code, there's no special APIs, no configuration files, builds
or hacks.
On Monday, February 4, 2013, mgutz wrote:
> How does this compare to node-webkit or appjs?
>
> On Monday, February 4, 2013 1:04:26 PM UTC-8, hi
*node-chrome(3)*
A tiny module for building desktop apps. It's really simple and uses the
chrome runtime.
*Here's the module.*
https://github.com/hij1nx/node-chrome/
*Here's an example.*
#!/usr/bin/env node
var cn = require('../lib');
var opts = {
runtime: "/Applications/Google\ Chrome.app/C
