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


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

Wait on keyboard

Started byjonas.thornvall@gmail.com
First post2016-03-11 02:30 -0800
Last post2016-03-14 18:58 +0800
Articles 20 on this page of 63 — 10 participants

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


Contents

  Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 02:30 -0800
    Re: Wait on keyboard Tim Streater <timstreater@greenbee.net> - 2016-03-11 10:37 +0000
    Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 02:50 -0800
      Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 03:13 -0800
        Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 03:23 -0800
          Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 03:32 -0800
            Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 03:39 -0800
              Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 04:41 -0800
                Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 05:00 -0800
                  Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 05:43 -0800
        Re: Wait on keyboard Tim Streater <timstreater@greenbee.net> - 2016-03-11 12:13 +0000
    Re: Wait on keyboard "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2016-03-11 21:52 +0800
      Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 07:29 -0800
    Re: Wait on keyboard Stefan Weiss <krewecherl@gmail.com> - 2016-03-11 17:00 +0100
      Re: Wait on keyboard Stefan Weiss <krewecherl@gmail.com> - 2016-03-11 17:11 +0100
        Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 08:32 -0800
          Re: Wait on keyboard Stefan Weiss <krewecherl@gmail.com> - 2016-03-11 20:20 +0100
        Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 08:55 -0800
          Re: Wait on keyboard Aleksandro <aleksandro@gmx.com> - 2016-03-11 16:30 -0300
            Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 11:46 -0800
              Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 12:22 -0800
                Re: Wait on keyboard Aleksandro <aleksandro@gmx.com> - 2016-03-11 17:25 -0300
                  Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 12:32 -0800
                    Re: Wait on keyboard Aleksandro <aleksandro@gmx.com> - 2016-03-11 17:42 -0300
                      Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 12:52 -0800
                    Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-11 12:47 -0800
                    Re: Wait on keyboard "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2016-03-11 18:39 -0800
                Re: Wait on keyboard "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2016-03-11 18:37 -0800
                Re: Wait on keyboard John Harris <niam@jghnorth.org.uk.invalid> - 2016-03-12 13:16 +0000
                  Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-12 05:57 -0800
                    Re: Wait on keyboard John Harris <niam@jghnorth.org.uk.invalid> - 2016-03-13 10:31 +0000
                      Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-13 05:55 -0700
                        Re: Wait on keyboard "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-03-13 17:19 +0100
                        Re: Wait on keyboard Scott Sauyet <scott.sauyet@gmail.com> - 2016-03-13 13:01 -0700
                          Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-13 15:19 -0700
                            Re: Wait on keyboard Aleksandro <aleksandro@gmx.com> - 2016-03-13 20:08 -0300
                              Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-13 21:45 -0700
                                Re: Wait on keyboard Aleksandro <aleksandro@gmx.com> - 2016-03-14 01:50 -0300
                                  Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-13 22:39 -0700
                                    Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-13 22:46 -0700
                                    Re: Wait on keyboard Scott Sauyet <scott.sauyet@gmail.com> - 2016-03-14 11:54 -0700
                                Re: Wait on keyboard Tim Streater <timstreater@greenbee.net> - 2016-03-14 08:31 +0000
                                Re: Wait on keyboard John Harris <niam@jghnorth.org.uk.invalid> - 2016-03-14 10:43 +0000
                  Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-12 06:04 -0800
                    Re: Wait on keyboard "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-03-12 15:22 +0100
                      Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-12 07:46 -0800
                        Re: Wait on keyboard Tim Streater <timstreater@greenbee.net> - 2016-03-12 15:52 +0000
                        Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-12 09:25 -0800
                          Re: Wait on keyboard Aleksandro <aleksandro@gmx.com> - 2016-03-12 20:16 -0300
                            Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-12 15:57 -0800
                              Re: Wait on keyboard Aleksandro <aleksandro@gmx.com> - 2016-03-12 21:07 -0300
                              Re: Wait on keyboard Scott Sauyet <scott.sauyet@gmail.com> - 2016-03-12 21:27 -0800
                                Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-13 03:08 -0700
                        Re: Wait on keyboard "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-03-12 23:30 +0100
                  Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-12 06:15 -0800
              Re: Wait on keyboard "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2016-03-11 18:33 -0800
                Re: Wait on keyboard jonas.thornvall@gmail.com - 2016-03-12 03:01 -0800
      Re: Wait on keyboard "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2016-03-11 18:30 -0800
      Re: Wait on keyboard Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-03-12 04:44 +0100
        Re: Wait on keyboard Stefan Weiss <krewecherl@gmail.com> - 2016-03-12 11:21 +0100
          Re: Wait on keyboard Stefan Weiss <krewecherl@gmail.com> - 2016-03-12 11:27 +0100
          Re: Wait on keyboard Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-03-12 14:44 +0100
      Re: Wait on keyboard "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2016-03-14 18:58 +0800

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →


#29916

Fromjonas.thornvall@gmail.com
Date2016-03-11 12:22 -0800
Message-ID<167d4204-d421-4852-ab16-b6659b83cfac@googlegroups.com>
In reply to#29915
Den fredag 11 mars 2016 kl. 20:46:31 UTC+1 skrev jonas.t...@gmail.com:
> Den fredag 11 mars 2016 kl. 20:30:40 UTC+1 skrev Aleksandro:
> > On 11/03/16 13:55, jonas.thornvall@gmail.com wrote:
> > > Den fredag 11 mars 2016 kl. 17:11:34 UTC+1 skrev Stefan Weiss:
> > >> On 03/11/2016 17:00, Stefan Weiss wrote:
> > >>>         sleepyFun.waitMouse = function (btn = 0) {
> > >>>             listen("click", (evt) => evt.button === btn);
> > >>>         };
> > >>
> > >> Whoops, default parameters aren't well supported yet... use this instead:
> > >>
> > >>         sleepyFun.waitMouse = function (btn) {
> > >>             listen("click", (evt) => evt.button === btn || 0);
> > >>         };
> > >>
> > >> - stefan
> > > 
> > > Sadly i think that Javascript is probably quite beautiful under the hood. Some where deep down there it is based upon sound principles, otherwise it would not have such rich functionality upon strings and arrays.
> > > 
> > > But sadly how weak and convoluted it ends up, when you put idiots to program the user interface, the actual program language. 
> > 
> > If you knew what you were talking about, you would know the UI events
> > have little do do with the actual language; they are merely an
> > implementation for a particular stack.
> 
> Well just as i told you, the idiots that implemented the eventhandler and listeners are not the same people that deigned the core language.

What actually happens is that some real bright people design a programming language programming languages by shape form and use mostly attract anal people who will celebrate its efficiensy, so after a couple of years "mostly one ot two" a comittee of idiots is appointed to develop the programming language, because lets face fact talented people do not have the attention spann to mull over simplistic matters for decades, they go on to solve nest problem after giving guidelines. 

So instead a committe of idiots is annnotated to do the bright man/mens work and it a month or two the idiots changed the guidelines into their own petty lifemission of linguistic pedantries transforming the language into an anal profession of hogwash that refuse to perform a command withoug at least 30 lines of code. 

Preferably the shit they produce should at least need a week or two to learn the API for howto take care of event handling, the first fucking week you spend try to catch the event and which button you actually pressed the second weekend should be spent finding out howto prepare the listener so when you press the damn key there is something actually there to catch the event.

I can recommend anyony to spend an extra week on finding out howto actually access the eventhandler. Because a simple keyPress will not do, no you should spend it to find out how the actual eventhandler will be accesed and howto awake the listener.

No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".

No these people want you to spend a week or two contemplaiting that you actually know what you want to do using a keypress becaus now it is ****their precikous programming language*****

Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.

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


#29917

FromAleksandro <aleksandro@gmx.com>
Date2016-03-11 17:25 -0300
Message-ID<nbv9eg$457$1@dont-email.me>
In reply to#29916
On 11/03/16 17:22, jonas.thornvall@gmail.com wrote:
> Den fredag 11 mars 2016 kl. 20:46:31 UTC+1 skrev jonas.t...@gmail.com:
>> Den fredag 11 mars 2016 kl. 20:30:40 UTC+1 skrev Aleksandro:
>>> On 11/03/16 13:55, jonas.thornvall@gmail.com wrote:
>>>> Den fredag 11 mars 2016 kl. 17:11:34 UTC+1 skrev Stefan Weiss:
>>>>> On 03/11/2016 17:00, Stefan Weiss wrote:
>>>>>>         sleepyFun.waitMouse = function (btn = 0) {
>>>>>>             listen("click", (evt) => evt.button === btn);
>>>>>>         };
>>>>>
>>>>> Whoops, default parameters aren't well supported yet... use this instead:
>>>>>
>>>>>         sleepyFun.waitMouse = function (btn) {
>>>>>             listen("click", (evt) => evt.button === btn || 0);
>>>>>         };
>>>>>
>>>>> - stefan
>>>>
>>>> Sadly i think that Javascript is probably quite beautiful under the hood. Some where deep down there it is based upon sound principles, otherwise it would not have such rich functionality upon strings and arrays.
>>>>
>>>> But sadly how weak and convoluted it ends up, when you put idiots to program the user interface, the actual program language. 
>>>
>>> If you knew what you were talking about, you would know the UI events
>>> have little do do with the actual language; they are merely an
>>> implementation for a particular stack.
>>
>> Well just as i told you, the idiots that implemented the eventhandler and listeners are not the same people that deigned the core language.
> 
> What actually happens is that some real bright people design a programming language programming languages by shape form and use mostly attract anal people who will celebrate its efficiensy, so after a couple of years "mostly one ot two" a comittee of idiots is appointed to develop the programming language, because lets face fact talented people do not have the attention spann to mull over simplistic matters for decades, they go on to solve nest problem after giving guidelines. 
> 
> So instead a committe of idiots is annnotated to do the bright man/mens work and it a month or two the idiots changed the guidelines into their own petty lifemission of linguistic pedantries transforming the language into an anal profession of hogwash that refuse to perform a command withoug at least 30 lines of code. 
> 
> Preferably the shit they produce should at least need a week or two to learn the API for howto take care of event handling, the first fucking week you spend try to catch the event and which button you actually pressed the second weekend should be spent finding out howto prepare the listener so when you press the damn key there is something actually there to catch the event.
> 
> I can recommend anyony to spend an extra week on finding out howto actually access the eventhandler. Because a simple keyPress will not do, no you should spend it to find out how the actual eventhandler will be accesed and howto awake the listener.
> 
> No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".
> 
> No these people want you to spend a week or two contemplaiting that you actually know what you want to do using a keypress becaus now it is ****their precikous programming language*****
> 
> Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.

Frustration speaking here.

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


#29918

Fromjonas.thornvall@gmail.com
Date2016-03-11 12:32 -0800
Message-ID<378139f6-98d2-45d8-b029-d56deef03f47@googlegroups.com>
In reply to#29917
Den fredag 11 mars 2016 kl. 21:25:52 UTC+1 skrev Aleksandro:
> On 11/03/16 17:22, jonas.thornvall@gmail.com wrote:
> > Den fredag 11 mars 2016 kl. 20:46:31 UTC+1 skrev jonas.t...@gmail.com:
> >> Den fredag 11 mars 2016 kl. 20:30:40 UTC+1 skrev Aleksandro:
> >>> On 11/03/16 13:55, jonas.thornvall@gmail.com wrote:
> >>>> Den fredag 11 mars 2016 kl. 17:11:34 UTC+1 skrev Stefan Weiss:
> >>>>> On 03/11/2016 17:00, Stefan Weiss wrote:
> >>>>>>         sleepyFun.waitMouse = function (btn = 0) {
> >>>>>>             listen("click", (evt) => evt.button === btn);
> >>>>>>         };
> >>>>>
> >>>>> Whoops, default parameters aren't well supported yet... use this instead:
> >>>>>
> >>>>>         sleepyFun.waitMouse = function (btn) {
> >>>>>             listen("click", (evt) => evt.button === btn || 0);
> >>>>>         };
> >>>>>
> >>>>> - stefan
> >>>>
> >>>> Sadly i think that Javascript is probably quite beautiful under the hood. Some where deep down there it is based upon sound principles, otherwise it would not have such rich functionality upon strings and arrays.
> >>>>
> >>>> But sadly how weak and convoluted it ends up, when you put idiots to program the user interface, the actual program language. 
> >>>
> >>> If you knew what you were talking about, you would know the UI events
> >>> have little do do with the actual language; they are merely an
> >>> implementation for a particular stack.
> >>
> >> Well just as i told you, the idiots that implemented the eventhandler and listeners are not the same people that deigned the core language.
> > 
> > What actually happens is that some real bright people design a programming language programming languages by shape form and use mostly attract anal people who will celebrate its efficiensy, so after a couple of years "mostly one ot two" a comittee of idiots is appointed to develop the programming language, because lets face fact talented people do not have the attention spann to mull over simplistic matters for decades, they go on to solve nest problem after giving guidelines. 
> > 
> > So instead a committe of idiots is annnotated to do the bright man/mens work and it a month or two the idiots changed the guidelines into their own petty lifemission of linguistic pedantries transforming the language into an anal profession of hogwash that refuse to perform a command withoug at least 30 lines of code. 
> > 
> > Preferably the shit they produce should at least need a week or two to learn the API for howto take care of event handling, the first fucking week you spend try to catch the event and which button you actually pressed the second weekend should be spent finding out howto prepare the listener so when you press the damn key there is something actually there to catch the event.
> > 
> > I can recommend anyony to spend an extra week on finding out howto actually access the eventhandler. Because a simple keyPress will not do, no you should spend it to find out how the actual eventhandler will be accesed and howto awake the listener.
> > 
> > No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".
> > 
> > No these people want you to spend a week or two contemplaiting that you actually know what you want to do using a keypress becaus now it is ****their precikous programming language*****
> > 
> > Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.
> 
> Frustration speaking here.

No actually it is the truth what requires 20 to 30 lines of javascript.
Could be achieved in a single line of *basic*

Go figure what kind of idiots responsible fot this.

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


#29919

FromAleksandro <aleksandro@gmx.com>
Date2016-03-11 17:42 -0300
Message-ID<nbvaek$8lo$1@dont-email.me>
In reply to#29918
On 11/03/16 17:32, jonas.thornvall@gmail.com wrote:
> Den fredag 11 mars 2016 kl. 21:25:52 UTC+1 skrev Aleksandro:
>> On 11/03/16 17:22, jonas.thornvall@gmail.com wrote:
>>> Den fredag 11 mars 2016 kl. 20:46:31 UTC+1 skrev jonas.t...@gmail.com:
>>>> Den fredag 11 mars 2016 kl. 20:30:40 UTC+1 skrev Aleksandro:
>>>>> On 11/03/16 13:55, jonas.thornvall@gmail.com wrote:
>>>>>> Den fredag 11 mars 2016 kl. 17:11:34 UTC+1 skrev Stefan Weiss:
>>>>>>> On 03/11/2016 17:00, Stefan Weiss wrote:
>>>>>>>>         sleepyFun.waitMouse = function (btn = 0) {
>>>>>>>>             listen("click", (evt) => evt.button === btn);
>>>>>>>>         };
>>>>>>>
>>>>>>> Whoops, default parameters aren't well supported yet... use this instead:
>>>>>>>
>>>>>>>         sleepyFun.waitMouse = function (btn) {
>>>>>>>             listen("click", (evt) => evt.button === btn || 0);
>>>>>>>         };
>>>>>>>
>>>>>>> - stefan
>>>>>>
>>>>>> Sadly i think that Javascript is probably quite beautiful under the hood. Some where deep down there it is based upon sound principles, otherwise it would not have such rich functionality upon strings and arrays.
>>>>>>
>>>>>> But sadly how weak and convoluted it ends up, when you put idiots to program the user interface, the actual program language. 
>>>>>
>>>>> If you knew what you were talking about, you would know the UI events
>>>>> have little do do with the actual language; they are merely an
>>>>> implementation for a particular stack.
>>>>
>>>> Well just as i told you, the idiots that implemented the eventhandler and listeners are not the same people that deigned the core language.
>>>
>>> What actually happens is that some real bright people design a programming language programming languages by shape form and use mostly attract anal people who will celebrate its efficiensy, so after a couple of years "mostly one ot two" a comittee of idiots is appointed to develop the programming language, because lets face fact talented people do not have the attention spann to mull over simplistic matters for decades, they go on to solve nest problem after giving guidelines. 
>>>
>>> So instead a committe of idiots is annnotated to do the bright man/mens work and it a month or two the idiots changed the guidelines into their own petty lifemission of linguistic pedantries transforming the language into an anal profession of hogwash that refuse to perform a command withoug at least 30 lines of code. 
>>>
>>> Preferably the shit they produce should at least need a week or two to learn the API for howto take care of event handling, the first fucking week you spend try to catch the event and which button you actually pressed the second weekend should be spent finding out howto prepare the listener so when you press the damn key there is something actually there to catch the event.
>>>
>>> I can recommend anyony to spend an extra week on finding out howto actually access the eventhandler. Because a simple keyPress will not do, no you should spend it to find out how the actual eventhandler will be accesed and howto awake the listener.
>>>
>>> No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".
>>>
>>> No these people want you to spend a week or two contemplaiting that you actually know what you want to do using a keypress becaus now it is ****their precikous programming language*****
>>>
>>> Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.
>>
>> Frustration speaking here.
> 
> No actually it is the truth what requires 20 to 30 lines of javascript.
> Could be achieved in a single line of *basic*
> 
> Go figure what kind of idiots responsible fot this.

And what requires 50 lines of code in your any other language of choice
can be done in a single one of Javascript.

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


#29921

Fromjonas.thornvall@gmail.com
Date2016-03-11 12:52 -0800
Message-ID<8abb9ce1-27aa-42f8-bd00-6781dd959c40@googlegroups.com>
In reply to#29919
Den fredag 11 mars 2016 kl. 21:43:01 UTC+1 skrev Aleksandro:
> On 11/03/16 17:32, jonas.thornvall@gmail.com wrote:
> > Den fredag 11 mars 2016 kl. 21:25:52 UTC+1 skrev Aleksandro:
> >> On 11/03/16 17:22, jonas.thornvall@gmail.com wrote:
> >>> Den fredag 11 mars 2016 kl. 20:46:31 UTC+1 skrev jonas.t...@gmail.com:
> >>>> Den fredag 11 mars 2016 kl. 20:30:40 UTC+1 skrev Aleksandro:
> >>>>> On 11/03/16 13:55, jonas.thornvall@gmail.com wrote:
> >>>>>> Den fredag 11 mars 2016 kl. 17:11:34 UTC+1 skrev Stefan Weiss:
> >>>>>>> On 03/11/2016 17:00, Stefan Weiss wrote:
> >>>>>>>>         sleepyFun.waitMouse = function (btn = 0) {
> >>>>>>>>             listen("click", (evt) => evt.button === btn);
> >>>>>>>>         };
> >>>>>>>
> >>>>>>> Whoops, default parameters aren't well supported yet... use this instead:
> >>>>>>>
> >>>>>>>         sleepyFun.waitMouse = function (btn) {
> >>>>>>>             listen("click", (evt) => evt.button === btn || 0);
> >>>>>>>         };
> >>>>>>>
> >>>>>>> - stefan
> >>>>>>
> >>>>>> Sadly i think that Javascript is probably quite beautiful under the hood. Some where deep down there it is based upon sound principles, otherwise it would not have such rich functionality upon strings and arrays.
> >>>>>>
> >>>>>> But sadly how weak and convoluted it ends up, when you put idiots to program the user interface, the actual program language. 
> >>>>>
> >>>>> If you knew what you were talking about, you would know the UI events
> >>>>> have little do do with the actual language; they are merely an
> >>>>> implementation for a particular stack.
> >>>>
> >>>> Well just as i told you, the idiots that implemented the eventhandler and listeners are not the same people that deigned the core language.
> >>>
> >>> What actually happens is that some real bright people design a programming language programming languages by shape form and use mostly attract anal people who will celebrate its efficiensy, so after a couple of years "mostly one ot two" a comittee of idiots is appointed to develop the programming language, because lets face fact talented people do not have the attention spann to mull over simplistic matters for decades, they go on to solve nest problem after giving guidelines. 
> >>>
> >>> So instead a committe of idiots is annnotated to do the bright man/mens work and it a month or two the idiots changed the guidelines into their own petty lifemission of linguistic pedantries transforming the language into an anal profession of hogwash that refuse to perform a command withoug at least 30 lines of code. 
> >>>
> >>> Preferably the shit they produce should at least need a week or two to learn the API for howto take care of event handling, the first fucking week you spend try to catch the event and which button you actually pressed the second weekend should be spent finding out howto prepare the listener so when you press the damn key there is something actually there to catch the event.
> >>>
> >>> I can recommend anyony to spend an extra week on finding out howto actually access the eventhandler. Because a simple keyPress will not do, no you should spend it to find out how the actual eventhandler will be accesed and howto awake the listener.
> >>>
> >>> No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".
> >>>
> >>> No these people want you to spend a week or two contemplaiting that you actually know what you want to do using a keypress becaus now it is ****their precikous programming language*****
> >>>
> >>> Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.
> >>
> >> Frustration speaking here.
> > 
> > No actually it is the truth what requires 20 to 30 lines of javascript.
> > Could be achieved in a single line of *basic*
> > 
> > Go figure what kind of idiots responsible fot this.
> 
> And what requires 50 lines of code in your any other language of choice
> can be done in a single one of Javascript.

Well that is still my point Aleksandro, the idiots that developed the array string handling are bright people, the idiots they put on listeners and eventhandling should be passed to a dark corner where they can thrive in linguistec waste garbage. 

Concat, pop, push, toString, toInt, subStr are all great ideas, maybe not  perfectly interfaced but at least they do not fucking need an API to be used.

The idiots that developed the interface for eventhandlers are basicly idiots.

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


#29920

Fromjonas.thornvall@gmail.com
Date2016-03-11 12:47 -0800
Message-ID<1c18d970-7be6-4ae0-ac0a-d49d5428c701@googlegroups.com>
In reply to#29918
Den fredag 11 mars 2016 kl. 21:32:49 UTC+1 skrev jonas.t...@gmail.com:
> Den fredag 11 mars 2016 kl. 21:25:52 UTC+1 skrev Aleksandro:
> > On 11/03/16 17:22, jonas.thornvall@gmail.com wrote:
> > > Den fredag 11 mars 2016 kl. 20:46:31 UTC+1 skrev jonas.t...@gmail.com:
> > >> Den fredag 11 mars 2016 kl. 20:30:40 UTC+1 skrev Aleksandro:
> > >>> On 11/03/16 13:55, jonas.thornvall@gmail.com wrote:
> > >>>> Den fredag 11 mars 2016 kl. 17:11:34 UTC+1 skrev Stefan Weiss:
> > >>>>> On 03/11/2016 17:00, Stefan Weiss wrote:
> > >>>>>>         sleepyFun.waitMouse = function (btn = 0) {
> > >>>>>>             listen("click", (evt) => evt.button === btn);
> > >>>>>>         };
> > >>>>>
> > >>>>> Whoops, default parameters aren't well supported yet... use this instead:
> > >>>>>
> > >>>>>         sleepyFun.waitMouse = function (btn) {
> > >>>>>             listen("click", (evt) => evt.button === btn || 0);
> > >>>>>         };
> > >>>>>
> > >>>>> - stefan
> > >>>>
> > >>>> Sadly i think that Javascript is probably quite beautiful under the hood. Some where deep down there it is based upon sound principles, otherwise it would not have such rich functionality upon strings and arrays.
> > >>>>
> > >>>> But sadly how weak and convoluted it ends up, when you put idiots to program the user interface, the actual program language. 
> > >>>
> > >>> If you knew what you were talking about, you would know the UI events
> > >>> have little do do with the actual language; they are merely an
> > >>> implementation for a particular stack.
> > >>
> > >> Well just as i told you, the idiots that implemented the eventhandler and listeners are not the same people that deigned the core language.
> > > 
> > > What actually happens is that some real bright people design a programming language programming languages by shape form and use mostly attract anal people who will celebrate its efficiensy, so after a couple of years "mostly one ot two" a comittee of idiots is appointed to develop the programming language, because lets face fact talented people do not have the attention spann to mull over simplistic matters for decades, they go on to solve nest problem after giving guidelines. 
> > > 
> > > So instead a committe of idiots is annnotated to do the bright man/mens work and it a month or two the idiots changed the guidelines into their own petty lifemission of linguistic pedantries transforming the language into an anal profession of hogwash that refuse to perform a command withoug at least 30 lines of code. 
> > > 
> > > Preferably the shit they produce should at least need a week or two to learn the API for howto take care of event handling, the first fucking week you spend try to catch the event and which button you actually pressed the second weekend should be spent finding out howto prepare the listener so when you press the damn key there is something actually there to catch the event.
> > > 
> > > I can recommend anyony to spend an extra week on finding out howto actually access the eventhandler. Because a simple keyPress will not do, no you should spend it to find out how the actual eventhandler will be accesed and howto awake the listener.
> > > 
> > > No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".
> > > 
> > > No these people want you to spend a week or two contemplaiting that you actually know what you want to do using a keypress becaus now it is ****their precikous programming language*****
> > > 
> > > Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.
> > 
> > Frustration speaking here.
> 
> No actually it is the truth what requires 20 to 30 lines of javascript.
> Could be achieved in a single line of *basic*
> 
> Go figure what kind of idiots responsible fot this.

Well it is a protest actually i will refuse to use the evenhandlers and listeners more than to a minimum extent. Until the monkeys who programmed it addressed both their own and their codes anal approach inadequasy and inefficiency.

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


#29926

From"Michael Haufe (TNO)" <tno@thenewobjective.com>
Date2016-03-11 18:39 -0800
Message-ID<d56c77b9-b43a-49ad-8f7a-4101201a8973@googlegroups.com>
In reply to#29918
On Friday, March 11, 2016 at 2:32:49 PM UTC-6, jonas.t...@gmail.com wrote:

> No actually it is the truth what requires 20 to 30 lines of javascript.
> Could be achieved in a single line of *basic*

or it just takes *you* 20-30 lines to accomplish it.

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


#29925

From"Michael Haufe (TNO)" <tno@thenewobjective.com>
Date2016-03-11 18:37 -0800
Message-ID<520d1d86-2471-469d-bf63-7563516c8664@googlegroups.com>
In reply to#29916
On Friday, March 11, 2016 at 2:22:38 PM UTC-6, jonas.t...@gmail.com wrote:
> What actually happens is that some real bright people design a programming language programming languages by shape form and use mostly attract anal people who will celebrate its efficiensy, so after a couple of years "mostly one ot two" a comittee of idiots is appointed to develop the programming language, because lets face fact talented people do not have the attention spann to mull over simplistic matters for decades, they go on to solve nest problem after giving guidelines. 

Once again, would you care to cite a single point of evidence which supports this?

> So instead a committe of idiots is annnotated to do the bright man/mens work and it a month or two the idiots changed the guidelines into their own petty lifemission of linguistic pedantries transforming the language into an anal profession of hogwash that refuse to perform a command withoug at least 30 lines of code. 
> 
> Preferably the shit they produce should at least need a week or two to learn the API for howto take care of event handling, the first fucking week you spend try to catch the event and which button you actually pressed the second weekend should be spent finding out howto prepare the listener so when you press the damn key there is something actually there to catch the event.
> 
> I can recommend anyony to spend an extra week on finding out howto actually access the eventhandler. Because a simple keyPress will not do, no you should spend it to find out how the actual eventhandler will be accesed and howto awake the listener.
> 
> No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".
> 
> No these people want you to spend a week or two contemplaiting that you actually know what you want to do using a keypress becaus now it is ****their precikous programming language*****
> 
> Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.

Perhaps you should stop drinking, or at least stay away from a computer when you do.

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


#29932

FromJohn Harris <niam@jghnorth.org.uk.invalid>
Date2016-03-12 13:16 +0000
Message-ID<re58ebtpclu82quc4thn4uglg7jp4ps48o@4ax.com>
In reply to#29916
On Fri, 11 Mar 2016 12:22:29 -0800 (PST), jonas.thornvall@gmail.com
wrote:

  <snip>
>No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".
  <snip>

You write 
  wait until (keypress==32);
in your program and it's legal because ECMAScript has been enhanced
the way you wanted. But your program is running in the web server and
there is *no* User Interface! 

What should the compiler do when it sees this? Obviously, it should
send an e-mail to the ECMA committee saying that they are bloody
idiots for putting such a stupid thing in the language.


>Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.

It looks as though the wakeup call has already hit a programmer who
splashes code down without thinking and then discovers the all too
predictable consequences.

  John

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


#29935

Fromjonas.thornvall@gmail.com
Date2016-03-12 05:57 -0800
Message-ID<19832681-7906-4fee-90ca-a01c88b9fa6e@googlegroups.com>
In reply to#29932
Den lördag 12 mars 2016 kl. 14:16:30 UTC+1 skrev John Harris:
> On Fri, 11 Mar 2016 12:22:29 -0800 (PST), jonas.thornvall@gmail.com
> wrote:
> 
>   <snip>
> >No these are anal people they can't fucking go for wait until (keypress=="32!) then do "what the fuck ever".
>   <snip>
> 
> You write 
>   wait until (keypress==32);
> in your program and it's legal because ECMAScript has been enhanced
> the way you wanted. But your program is running in the web server and
> there is *no* User Interface! 

Your just silly there is no user interface to catch an alert on server either. So you say that javascript somehow immune to do weird things on server? Well if so that would need some sort of exception for UI code in general executed on server and then you could as well incorporate wait and keypress. If it is the fact you do not like wait without a time that is easily fixed.

> What should the compiler do when it sees this? Obviously, it should
> send an e-mail to the ECMA committee saying that they are bloody
> idiots for putting such a stupid thing in the language.

Well what about an alert running at server. What about any UI event on server.
> 
> >Well you retarded, anal *MOTHERFUCKERS* are in for a wakeup call.
> 
> It looks as though the wakeup call has already hit a programmer who
> splashes code down without thinking and then discovers the all too
> predictable consequences.
> 
>   John

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


#29954

FromJohn Harris <niam@jghnorth.org.uk.invalid>
Date2016-03-13 10:31 +0000
Message-ID<bbgaeblqc1s0d6inalb50oduink406pdf9@4ax.com>
In reply to#29935
On Sat, 12 Mar 2016 05:57:40 -0800 (PST), jonas.thornvall@gmail.com
wrote:

  <snip>
>Well what about an alert running at server.
  <snip>

If you search ECMA 262 you will find that the word "alert" does not
appear anywhere in the ECMAScript standard.

Therefore, alert is not part of the ECMAScript core language. It is a
function supplied to programs by the browser in the same way that
objects giving you access to the document are supplied by the browser.

In a server either there is no function named alert or it is a
function that does something different.

  John

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


#29960

Fromjonas.thornvall@gmail.com
Date2016-03-13 05:55 -0700
Message-ID<040dba52-3121-4d6e-850e-ef5aa64147e2@googlegroups.com>
In reply to#29954
Den söndag 13 mars 2016 kl. 11:31:29 UTC+1 skrev John Harris:
> On Sat, 12 Mar 2016 05:57:40 -0800 (PST), jonas.thornvall@gmail.com
> wrote:
> 
>   <snip>
> >Well what about an alert running at server.
>   <snip>
> 
> If you search ECMA 262 you will find that the word "alert" does not
> appear anywhere in the ECMAScript standard.
> 
> Therefore, alert is not part of the ECMAScript core language. It is a
> function supplied to programs by the browser in the same way that
> objects giving you access to the document are supplied by the browser.
> 
> In a server either there is no function named alert or it is a
> function that does something different.
> 
>   John

Well i guess there is no eventhandlers either running on the server. And that is my point the listeners and evenhandler UI should have both *wait* and *keypress*

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


#29964

From"Evertjan." <exxjxw.hannivoort@inter.nl.net>
Date2016-03-13 17:19 +0100
Message-ID<XnsA5CAB049FA4Eeejj99@194.109.6.166>
In reply to#29960
jonas.thornvall@gmail.com wrote on 13 Mar 2016 in comp.lang.javascript:

> Well i guess there is no eventhandlers either running on the server. And
> that is my point the listeners and evenhandler UI should have both
> *wait* and *keypress* 

Nonsense. You guess wrong.

Eventhandlers are not "running" they are called by the browser when an event 
takes place someway like this:

The browser looks after each event if there is an handler registered,
and then the registered piece of Javascript is called to run.

*wait* and *keypress* presuppose a running Javascript, which would be a 
waist of resources, as such event may never  come ore take a long time to 
come. Javascript in a browser [and mostly elswhere too, I suppose] ends when 
finished and takes up no resourses after that time.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

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


#29967

FromScott Sauyet <scott.sauyet@gmail.com>
Date2016-03-13 13:01 -0700
Message-ID<332117cd-e7df-4f7f-b03b-0022d6229e02@googlegroups.com>
In reply to#29960
jonas.thornvall@gmail.com wrote: 
> John Harris wrote:

>> If you search ECMA 262 you will find that the word "alert" does not
>> appear anywhere in the ECMAScript standard.
>> 
>> Therefore, alert is not part of the ECMAScript core language. It is a
>> function supplied to programs by the browser in the same way that
>> objects giving you access to the document are supplied by the browser.
>> 
>> In a server either there is no function named alert or it is a
>> function that does something different.
> 
> Well i guess there is no eventhandlers either running on the server. 
> And that is my point the listeners and evenhandler UI should have 
> both *wait* and *keypress*

Why?  For heaven's sake, why should it have your "keypress" and not my
"mousemove", her "resize", his "touch", their "click", or everyone's
"change" actions?  Or are you suggesting that it should have all of 
them as top-level events, and then every time someone needs a new
event we have to expand this API?

And what are your semantics for "wait" in a single-threaded language?
What does it mean?  How does it affect the rest of the host environment
(browser, server, other) where the Javascript runs?  Are you talking
about something like continuations, or do you really expect to pause
the entire execution of the engine while you wait for your 
prince^B^B^B^B^B event to come?

Or are you simply whining, "This is not working like some other 
language I used to know, and I don't want to bother learning anything
about this one?  Why can't someone fix this so I don't have to bother
using my brain?  Come on guys, help me out?  Please?"

Because that's certainly what it sounds like.

  -- Scott

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


#29968

Fromjonas.thornvall@gmail.com
Date2016-03-13 15:19 -0700
Message-ID<176191a9-82a7-48b1-affb-e9053c66f4d2@googlegroups.com>
In reply to#29967
Den söndag 13 mars 2016 kl. 21:01:18 UTC+1 skrev Scott Sauyet:
> jonas.thornvall@gmail.com wrote: 
> > John Harris wrote:
> 
> >> If you search ECMA 262 you will find that the word "alert" does not
> >> appear anywhere in the ECMAScript standard.
> >> 
> >> Therefore, alert is not part of the ECMAScript core language. It is a
> >> function supplied to programs by the browser in the same way that
> >> objects giving you access to the document are supplied by the browser.
> >> 
> >> In a server either there is no function named alert or it is a
> >> function that does something different.
> > 
> > Well i guess there is no eventhandlers either running on the server. 
> > And that is my point the listeners and evenhandler UI should have 
> > both *wait* and *keypress*
> 
> Why?  For heaven's sake, why should it have your "keypress" and not my
> "mousemove", her "resize", his "touch", their "click", or everyone's
> "change" actions?  Or are you suggesting that it should have all of 
> them as top-level events, and then every time someone needs a new
> event we have to expand this API?
> 
> And what are your semantics for "wait" in a single-threaded language?
> What does it mean?  How does it affect the rest of the host environment
> (browser, server, other) where the Javascript runs?  Are you talking
> about something like continuations, or do you really expect to pause
> the entire execution of the engine while you wait for your 
> prince^B^B^B^B^B event to come?
> 
> Or are you simply whining, "This is not working like some other 
> language I used to know, and I don't want to bother learning anything
> about this one?  Why can't someone fix this so I don't have to bother
> using my brain?  Come on guys, help me out?  Please?"
> 
> Because that's certainly what it sounds like.
> 
>   -- Scott

Honestly i don't anything as long it does not invoke 30 lines of code  to wait for user input. And it is a keyboard i do not see why it is tied to fields and documents only. I wano to call functions on presskey.

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


#29969

FromAleksandro <aleksandro@gmx.com>
Date2016-03-13 20:08 -0300
Message-ID<nc4rnk$3kt$1@dont-email.me>
In reply to#29968
On 13/03/16 19:19, jonas.thornvall@gmail.com wrote:
> I wano to call functions on presskey.

And your problem is...?

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


#29972

Fromjonas.thornvall@gmail.com
Date2016-03-13 21:45 -0700
Message-ID<c0352a15-5432-436a-8b29-823c9518050a@googlegroups.com>
In reply to#29969
Den måndag 14 mars 2016 kl. 00:08:38 UTC+1 skrev Aleksandro:
> On 13/03/16 19:19, jonas.thornvall@gmail.com wrote:
> > I wano to call functions on presskey.
> 
> And your problem is...?
That the examples i find want to me to be in a textfield or use another "id" element to reach the keylisteener. There is no global keylistener?

Or?

<input type="text" onKeyPress="alert(this.value)">
<input type="text" onKeyPress="handleInput(this.value)">

function handleInput(value){
    alert(value);
}

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


#29973

FromAleksandro <aleksandro@gmx.com>
Date2016-03-14 01:50 -0300
Message-ID<nc5fnv$mb4$1@dont-email.me>
In reply to#29972
On 14/03/16 01:45, jonas.thornvall@gmail.com wrote:
> Den måndag 14 mars 2016 kl. 00:08:38 UTC+1 skrev Aleksandro:
>> On 13/03/16 19:19, jonas.thornvall@gmail.com wrote:
>>> I wano to call functions on presskey.
>>
>> And your problem is...?
> That the examples i find want to me to be in a textfield or use another "id" element to reach the keylisteener. There is no global keylistener?

That's why I told you to look up what event bubbling is!!!

> Or?
> 
> <input type="text" onKeyPress="alert(this.value)">
> <input type="text" onKeyPress="handleInput(this.value)">
> 
> function handleInput(value){
>     alert(value);
> }

That's horrible. lol

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


#29974

Fromjonas.thornvall@gmail.com
Date2016-03-13 22:39 -0700
Message-ID<95865a2a-5433-446a-a4b3-c6f4c48d1afd@googlegroups.com>
In reply to#29973
Den måndag 14 mars 2016 kl. 05:50:09 UTC+1 skrev Aleksandro:
> On 14/03/16 01:45, jonas.thornvall@gmail.com wrote:
> > Den måndag 14 mars 2016 kl. 00:08:38 UTC+1 skrev Aleksandro:
> >> On 13/03/16 19:19, jonas.thornvall@gmail.com wrote:
> >>> I wano to call functions on presskey.
> >>
> >> And your problem is...?
> > That the examples i find want to me to be in a textfield or use another "id" element to reach the keylisteener. There is no global keylistener?
> 
> That's why I told you to look up what event bubbling is!!!
Well i do acknowledge that you people "you know who you are" celebrate your convoluted workarounds dealing with simple matters, what i can see at glance is at bubbling probably is a way to create a scope for the eventlisteners.

But my question remain, why isn't there a general keyboard listener? I mean maybe i do not have any elements to listen upon. I want to listen to the keyboard.
 
> > Or?
> > 
> > <input type="text" onKeyPress="alert(this.value)">
> > <input type="text" onKeyPress="handleInput(this.value)">
> > 
> > function handleInput(value){
> >     alert(value);
> > }
> 
> That's horrible. lol

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


#29975

Fromjonas.thornvall@gmail.com
Date2016-03-13 22:46 -0700
Message-ID<fae6cdd2-c1db-4987-8f9b-f05376bc766b@googlegroups.com>
In reply to#29974
Den måndag 14 mars 2016 kl. 06:39:38 UTC+1 skrev jonas.t...@gmail.com:
> Den måndag 14 mars 2016 kl. 05:50:09 UTC+1 skrev Aleksandro:
> > On 14/03/16 01:45, jonas.thornvall@gmail.com wrote:
> > > Den måndag 14 mars 2016 kl. 00:08:38 UTC+1 skrev Aleksandro:
> > >> On 13/03/16 19:19, jonas.thornvall@gmail.com wrote:
> > >>> I wano to call functions on presskey.
> > >>
> > >> And your problem is...?
> > > That the examples i find want to me to be in a textfield or use another "id" element to reach the keylisteener. There is no global keylistener?
> > 
> > That's why I told you to look up what event bubbling is!!!
> Well i do acknowledge that you people "you know who you are" celebrate your convoluted workarounds dealing with simple matters, what i can see at glance is at bubbling probably is a way to create a scope for the eventlisteners.
> 
> But my question remain, why isn't there a general keyboard listener? I mean maybe i do not have any elements to listen upon. I want to listen to the keyboard.
>  
> > > Or?
> > > 
> > > <input type="text" onKeyPress="alert(this.value)">
> > > <input type="text" onKeyPress="handleInput(this.value)">
> > > 
> > > function handleInput(value){
> > >     alert(value);
> > > }
> > 
> > That's horrible. lol

I think Scott arguments regarding wait in javascript, was that people would use wait maliciously on webpages, but why bother you can create a loop that make it hang anyday?

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


Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

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


csiph-web