Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #21943 > unrolled thread

Is it possible to pop up windows in node.js?

Back to article view | Back to comp.lang.javascript

Contents

  Is it possible to pop up windows in node.js? bit-naughty@hotmail.com - 2013-11-09 07:42 -0800
    Re: Is it possible to pop up windows in node.js? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2013-11-10 23:24 -0800
      Re: Is it possible to pop up windows in node.js? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-11 10:16 +0100
        Re: Is it possible to pop up windows in node.js? "Evertjan." <exjxw.hannivoort@interxnl.net> - 2013-11-11 12:31 +0000
        Re: Is it possible to pop up windows in node.js? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2013-11-11 08:26 -0800
          Re: Is it possible to pop up windows in node.js? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-11 17:32 +0100
            Re: Is it possible to pop up windows in node.js? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2013-11-11 10:06 -0800
              Re: Is it possible to pop up windows in node.js? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-11 20:21 +0100
                Re: Is it possible to pop up windows in node.js? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2013-11-11 12:49 -0800
                  Re: Is it possible to pop up windows in node.js? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-11 22:52 +0100
                    Re: Is it possible to pop up windows in node.js? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2013-11-11 17:14 -0800

#21943 — Is it possible to pop up windows in node.js?

.... I don't know practically the 1st thing about it, but know it's for servers. Which is why I'm curious to know if GUI stuff can be done.


Thanks :)

[toc] | [next] | [standalone]

#21958

On Saturday, November 9, 2013 9:42:41 AM UTC-6, bit-n...@hotmail.com wrote:
> .... I don't know practically the 1st thing about it, but know it's for servers. Which is why I'm curious to know if GUI stuff can be done.

Have you done any server programming in the past in other languages/technologies? If so the basic concepts are similar, otherwise I think even the simplest answer is going to raise even more questions. Also, you aren't limited to servers. So the quick answer is yes.

[toc] | [prev] | [next] | [standalone]

#21960

Michael Haufe (TNO) wrote:

> On Saturday, November 9, 2013 9:42:41 AM UTC-6, bit-n...@hotmail.com
> wrote:
>> .... I don't know practically the 1st thing about it, but know it's for
>> servers. Which is why I'm curious to know if GUI stuff can be done.
> 
> Have you done any server programming in the past in other
> languages/technologies? If so the basic concepts are similar, otherwise I
> think even the simplest answer is going to raise even more questions.
> Also, you aren't limited to servers. So the quick answer is yes.

How do you “pop-up windows *in* node.js”?

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#21961

Thomas 'PointedEars' Lahn wrote on 11 nov 2013 in comp.lang.javascript:

> How do you ƒ opop-up windows *in* node.jsƒ  ?

Simple, the popup will show on the server's monitor, if available to the 
server AND to the server programme, both availabilities usually and 
blissfully absent in virtual server farms.

And even if so, who would press the okay-button? 

Evertjan.

[toc] | [prev] | [next] | [standalone]

#21962

On Monday, November 11, 2013 3:16:25 AM UTC-6, Thomas 'PointedEars' Lahn wrote:

> How do you “pop-up windows *in* node.js”?

By the usual way for a traditional HTML browser <-> server setup using a request/response relationship. Off the cuff:

var http = require("http");
var server = http.createServer(function(request, response) {
  response.writeHead(200, {"Content-Type": "text/html"});
  response.write(
  "<!DOCTYPE html>" +
  "<html lang='en' dir='ltr'>" +
    "<head>" +
      "<met charset='utf-8'>" +
      "<title>Hola Mundo</title>" +
    "</head>" +
    "<body>" +
      "<script type='text/javascript'>alert('Hello World')</script>" +
  "</body>" +
  "</html>");
  response.end();
});
 
server.listen(80);

For a non-server setup: one can use the functionality of one of the numerous GUI frameworks:

<https://github.com/zcbenz/node-gui/#a-simple-example>

[toc] | [prev] | [next] | [standalone]

#21963

Michael Haufe (TNO) wrote:

> Thomas 'PointedEars' Lahn wrote:
>> How do you “pop-up windows *in* node.js”?
> 
> By the usual way for a traditional HTML browser <-> server setup using a
> request/response relationship. Off the cuff:
> 
> var http = require("http");
> var server = http.createServer(function(request, response) {
>   response.writeHead(200, {"Content-Type": "text/html"});
>   response.write(
>   "<!DOCTYPE html>" +
>   "<html lang='en' dir='ltr'>" +
>     "<head>" +
>       "<met charset='utf-8'>" +
>       "<title>Hola Mundo</title>" +
>     "</head>" +
>     "<body>" +
>       "<script type='text/javascript'>alert('Hello World')</script>" +
>   "</body>" +
>   "</html>");
>   response.end();
> });
>  
> server.listen(80);

Because I expected something simple like this, I had emphasized *in*.  This 
is not popping up a window *in* node.js, it is popping up one *with the help 
of* node.js.
 
> For a non-server setup: one can use the functionality of one of the
> numerous GUI frameworks:
> 
> <https://github.com/zcbenz/node-gui/#a-simple-example>

ACK.  It is, however, not enough to justify your “yes”.

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#21964

On Monday, November 11, 2013 10:32:11 AM UTC-6, Thomas 'PointedEars' Lahn wrote:

> Because I expected something simple like this, I had emphasized *in*.  This 
> is not popping up a window *in* node.js, it is popping up one *with the help 
> of* node.js.

That's like saying using "window.alert" or "WScript.Echo" is not popping up a window *in* JS, but *with the help of* JS. This is a tedious detail which is elided as it does not advance or answer the main question in a meaningful way. Additionally, I'm relatively certain the OP used the word "in" to mean "in the context of". So if he/she hasn't been scared off by the meta-discussion, we might get a follow-up.

> ACK.  It is, however, not enough to justify your “yes”.

Pretty sure I said "the quick answer is yes"

Do you have a more constructive answer towards the original question?

[toc] | [prev] | [next] | [standalone]

#21965

Michael Haufe (TNO) wrote:

> Thomas 'PointedEars' Lahn wrote:
>> Because I expected something simple like this, I had emphasized *in*. 
>> This is not popping up a window *in* node.js, it is popping up one *with
>> the help of* node.js.
> 
> That's like saying using "window.alert" or "WScript.Echo" is not popping
> up a window *in* JS, but *with the help of* JS.

Apples and oranges.  node.js in this case merely generates code that is 
executed somewhere else.

> This is a tedious detail

No, it is not.

> which is elided as it does not advance or answer the main question in a
> meaningful way.

IYHO.

> Additionally, I'm relatively certain the OP used the word "in" to mean "in
> the context of".

I am 99.2% certain the OP has not the slightest clue what they are talking 
about.  Insofar, barring a server-side API for node.js to pop up windows, it 
would be better to educate them as to server-side and client-side code.

> So if he/she hasn't been scared off by the meta-discussion, we might get a
> follow-up.

There you go again.  If you can't stand the heat, stay out of the kitchen.
 
>> ACK.  It is, however, not enough to justify your “yes”.
> 
> Pretty sure I said "the quick answer is yes"

Whereas IMHO the “quick answer” therefore must be “no”.
 
> Do you have a more constructive answer towards the original question?

Not having dealt with node.js yet, and not being in the habit of helping 
anonymous Google lusers, no.

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#21966

On Monday, November 11, 2013 1:21:46 PM UTC-6, Thomas 'PointedEars' Lahn wrote:
> Michael Haufe (TNO) wrote:

> Apples and oranges.  node.js in this case merely generates code that is 
> executed somewhere else.

Don't confuse analogy with equivalence

> > This is a tedious detail
>
> No, it is not.

IYHO

> > So if he/she hasn't been scared off by the meta-discussion, we might get a
> > follow-up.
> 
> There you go again.  If you can't stand the heat, stay out of the kitchen.

s/heat/noise

> I am 99.2% certain the OP has not the slightest clue what they are talking 
> about. [...]

Being as pedantic as you are, it's curious you'd open yourself up like this.

> [...] and not being in the habit of helping 
> anonymous Google lusers, no.

Then why bother replying at all if you have nothing useful to add?

[toc] | [prev] | [next] | [standalone]

#21968

Michael Haufe (TNO) wrote:

> Thomas 'PointedEars' Lahn wrote:
>> [...] and not being in the habit of helping anonymous Google lusers, no.
> 
> Then why bother replying at all if you have nothing useful to add?

Wrong answers are bad.  Misleading answers doubly so.

Perhaps I should start filtering out non-anonymous Google lusers as well.

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#21978

On Monday, November 11, 2013 3:52:26 PM UTC-6, Thomas 'PointedEars' Lahn wrote:
>
> Perhaps I should start filtering out non-anonymous Google lusers as well.

I agree.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web