Using Express and how to prevent "accept incoming network connections" question.

[0x80]

Hi,

I've just started playing around with node-webkit. I am planning to make an app based on express. When the node-webkit application loaded my script for the first time, it asked me "do you want node-webkit to accept incoming network connections?" or something similar. 

I only want to communicate between my interface and express locally, and for a few things call an external service from node. I don't need to have express act as a server to the outside. Is there a way to prevent this message from appearing in OSX? Can I configure my app so that is doesn't scare people. They would not expect this message based on the context of my app.

Cheers

[Tom Moor]

I believe the only way to stop this message is to sign your application.

[Thijs Koerselman]

I have a feeling I'm missing something fundamental about this whole webkit approach. 

In a web app you usually interact from the interface with some server either using generated content by something like express or using a client library like backbone to fetch data using a service interface.

When I want to create a desktop app using standard tools like this, I would need a web server to back it up, right? So I'm thinking most desktop apps created with node-webkit would have this problem? How do you create your app interface using standard frameworks and libraries without instantiating a webserver and generating this kind of warnings?

--
You received this message because you are subscribed to a topic in the Google Groups "node-webkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-webkit/8ojhhkxw1Oo/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to node-webkit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[0x80]

On Wednesday, May 1, 2013 10:19:00 PM UTC+2, 0x80 wrote:

I have a feeling I'm missing something fundamental about this whole webkit approach. 

In a web app you usually interact from the interface with some server either using generated content by something like express or using a client library like backbone to fetch data using a service interface.

When I want to create a desktop app using standard tools like this, I would need a web server to back it up, right? So I'm thinking most desktop apps created with node-webkit would have this problem? How do you create your app interface using standard frameworks and libraries without instantiating a webserver and generating this kind of warnings?

I think I get the idea now. Meanwhile I found the nw-sample-apps repository and read about the native ui api. I guess I was wrong thinking that it makes sense to use something like express or backbone to build your app gui logic. I should use the native ui tools and straight javascript instead, without passing data through a server port.

[Tom Moor]

The Native UI API really only deals with things that lie outside your main application, the window frame, clipboard, taskbar, alerts etc. 

I would still highly recommend using a javascript framework like backbone to structure your UI logic - however as you say there isn't really any need for a client/server architecture. Just perform all of your logic / persistence etc in the 'client'.

Hope this helps.

--