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

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

Breaking up the HTML into logical blocks.

Started byJonas Thörnvall <jonas.thornvall@gmail.com>
First post2019-03-27 22:26 -0700
Last post2019-03-29 10:32 -0700
Articles 20 on this page of 93 — 4 participants

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

Contents

  Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-27 22:26 -0700
    Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 01:19 -0700
      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 01:53 -0700
        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 02:14 -0700
          Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-28 02:47 -0700
            Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 03:20 -0700
              Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-28 04:49 -0700
                Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:03 -0700
                  Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:12 -0700
                    Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:13 -0700
                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:19 -0700
                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:24 -0700
                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:32 -0700
                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:37 -0700
                          Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:39 -0700
                    Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-28 05:20 -0700
                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:26 -0700
                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 05:46 -0700
                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 06:29 -0700
                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 07:21 -0700
                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 07:26 -0700
                          Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 07:34 -0700
                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 20:41 -0700
                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 20:46 -0700
            Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 03:28 -0700
              Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-28 03:35 -0700
                Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-28 04:55 -0700
                  Re: Breaking up the HTML into logical blocks. "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-03-29 09:11 +0100
                    Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 02:14 -0700
                      Re: Breaking up the HTML into logical blocks. "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-03-29 10:54 +0100
                        Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 10:05 -0700
                          Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 10:43 -0700
                            Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 11:01 -0700
                              Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 11:38 -0700
                              Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 12:25 -0700
                                Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 12:37 -0700
                            Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 11:42 -0700
                              Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 12:30 -0700
                                Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 12:36 -0700
                                  Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 12:38 -0700
                                    Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 12:41 -0700
                                    Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 12:43 -0700
                                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 12:49 -0700
                                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 12:54 -0700
                                          Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 12:58 -0700
                                            Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 13:04 -0700
                                              Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 13:10 -0700
                                    Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 12:45 -0700
                                      Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 12:50 -0700
                                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 13:01 -0700
                                          Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 13:04 -0700
                                            Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 13:07 -0700
                                              Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 13:12 -0700
                                                Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 13:14 -0700
                                                  Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 13:22 -0700
                                                Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 13:18 -0700
                                                  Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 13:23 -0700
                                                    Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 13:31 -0700
                                                    Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-29 13:32 -0700
                                                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 14:10 -0700
                                                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 14:19 -0700
                                                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 14:23 -0700
                                                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 14:38 -0700
                                                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 14:42 -0700
                                                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 00:40 -0700
                                                        Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-30 01:37 -0700
                                                          Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 03:00 -0700
                                                            Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 03:36 -0700
                                                              Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-30 05:36 -0700
                                                                Re: Breaking up the HTML into logical blocks. dr.j.r.stockton@gmail.com - 2019-03-30 07:09 -0700
                                                                Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 07:16 -0700
                                                                Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 07:25 -0700
                                                                  Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 07:32 -0700
                                                                    Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 07:46 -0700
                                                                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 08:21 -0700
                                                                  Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-31 02:16 -0700
                                                                    Re: Breaking up the HTML into logical blocks. "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-03-31 11:26 +0200
                                                                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-31 07:07 -0700
                                                                Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 07:26 -0700
                                                      Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 00:51 -0700
                                                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 01:21 -0700
                                                        Re: Breaking up the HTML into logical blocks. Julio Di Egidio <julio@diegidio.name> - 2019-03-30 01:31 -0700
                                                          Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 02:34 -0700
                                                          Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 02:46 -0700
                                                            Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-30 02:58 -0700
                    Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 02:22 -0700
                      Re: Breaking up the HTML into logical blocks. "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-03-29 11:03 +0100
                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 08:41 -0700
                        Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 08:51 -0700
                          Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 09:11 -0700
                          Re: Breaking up the HTML into logical blocks. "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-03-29 17:18 +0100
                            Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 10:31 -0700
                            Re: Breaking up the HTML into logical blocks. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-03-29 10:32 -0700

Page 1 of 5  [1] 2 3 4 5  Next page →

#36195 — Breaking up the HTML into logical blocks.

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-27 22:26 -0700
SubjectBreaking up the HTML into logical blocks.
Message-ID<aa9e9f99-aee9-46aa-aa5c-e596794a57f7@googlegroups.com>
When programming my scripts and matching HTML, i've noticed that with an application sized HTML structure it is quite beneficial for me to break up the script part into a logical structure of script sources that i load from start.

However as the complexity groves also the HTML that holds canvas, inputs, outputs also groves with the application. And i can feel the necessity to split up the bulk block of HTML, into logical functional subblocks.

I mean why should i have the HTML that deals with editing, animation, setting e.t.c in same block?

I thought the way to do it was by split up the HTML block into subblocks, that could be loaded as innerHTML into the mainblock.

But my innerHTML subblocks also hold function calls to the main HTML file "outerHTML?", and i now realised i don't know howto call the script invoked in outerHTML block from the innerHTML block.

Now someone probably say i should skip HTML and make CSS, but i am really not keen on add complexity that is not necessary. I have some CSS for mouseevent handling, but i do not want any where it is not needed.


Can i reach the script loaded in outerHTML from the innerHTML loaded page "what is the parameters"? If not what approach should i take to split up the main HTML text block into logical subs.

Here is how i load the innerHTML blocks into the outer main block.Not that it matter but the blocks are logical units hidden in buttons.

document.getElementById("mousedrum").innerHTML='<object style="min-width:100%; min-height: 300; type="text/html" data="virtkeyb.html"  ></object>';

JT

[toc] | [next] | [standalone]

#36196

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 01:19 -0700
Message-ID<0123f587-19e7-4d09-807e-8fc7a4389b02@googlegroups.com>
In reply to#36195
Den torsdag 28 mars 2019 kl. 06:26:42 UTC+1 skrev Jonas Thörnvall:
> When programming my scripts and matching HTML, i've noticed that with an application sized HTML structure it is quite beneficial for me to break up the script part into a logical structure of script sources that i load from start.
> 
> However as the complexity groves also the HTML that holds canvas, inputs, outputs also groves with the application. And i can feel the necessity to split up the bulk block of HTML, into logical functional subblocks.
> 
> I mean why should i have the HTML that deals with editing, animation, setting e.t.c in same block?
> 
> I thought the way to do it was by split up the HTML block into subblocks, that could be loaded as innerHTML into the mainblock.
> 
> But my innerHTML subblocks also hold function calls to the main HTML file "outerHTML?", and i now realised i don't know howto call the script invoked in outerHTML block from the innerHTML block.
> 
> Now someone probably say i should skip HTML and make CSS, but i am really not keen on add complexity that is not necessary. I have some CSS for mouseevent handling, but i do not want any where it is not needed.
> 
> 
> Can i reach the script loaded in outerHTML from the innerHTML loaded page "what is the parameters"? If not what approach should i take to split up the main HTML text block into logical subs.
> 
> Here is how i load the innerHTML blocks into the outer main block.Not that it matter but the blocks are logical units hidden in buttons.
> 
> document.getElementById("mousedrum").innerHTML='<object style="min-width:100%; min-height: 300; type="text/html" data="virtkeyb.html"  ></object>';
> 
> JT

I just tested insert an import link into the HTML   
<link rel="import" href="virtKeyb.html" >

Gives me
sequenser.html:1 Access to imported resource at 'file:///C:/Users/jonas/Desktop/KOD%20p%C3%A5g%C3%A5ende/27%20Mars/virtKeyb.html' from origin 'null' has been blocked by CORS policy: The response is invalid.
virtKeyb.html:1
 Failed to load resource: net::ERR_FAILED

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

#36197

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 01:53 -0700
Message-ID<e8e3368b-efdb-49ba-b5b5-3b517073c428@googlegroups.com>
In reply to#36196
Den torsdag 28 mars 2019 kl. 09:19:31 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 06:26:42 UTC+1 skrev Jonas Thörnvall:
> > When programming my scripts and matching HTML, i've noticed that with an application sized HTML structure it is quite beneficial for me to break up the script part into a logical structure of script sources that i load from start.
> > 
> > However as the complexity groves also the HTML that holds canvas, inputs, outputs also groves with the application. And i can feel the necessity to split up the bulk block of HTML, into logical functional subblocks.
> > 
> > I mean why should i have the HTML that deals with editing, animation, setting e.t.c in same block?
> > 
> > I thought the way to do it was by split up the HTML block into subblocks, that could be loaded as innerHTML into the mainblock.
> > 
> > But my innerHTML subblocks also hold function calls to the main HTML file "outerHTML?", and i now realised i don't know howto call the script invoked in outerHTML block from the innerHTML block.
> > 
> > Now someone probably say i should skip HTML and make CSS, but i am really not keen on add complexity that is not necessary. I have some CSS for mouseevent handling, but i do not want any where it is not needed.
> > 
> > 
> > Can i reach the script loaded in outerHTML from the innerHTML loaded page "what is the parameters"? If not what approach should i take to split up the main HTML text block into logical subs.
> > 
> > Here is how i load the innerHTML blocks into the outer main block.Not that it matter but the blocks are logical units hidden in buttons.
> > 
> > document.getElementById("mousedrum").innerHTML='<object style="min-width:100%; min-height: 300; type="text/html" data="virtkeyb.html"  ></object>';
> > 
> > JT
> 
> I just tested insert an import link into the HTML   
> <link rel="import" href="virtKeyb.html" >
> 
> Gives me
> sequenser.html:1 Access to imported resource at 'file:///C:/Users/jonas/Desktop/KOD%20p%C3%A5g%C3%A5ende/27%20Mars/virtKeyb.html' from origin 'null' has been blocked by CORS policy: The response is invalid.
> virtKeyb.html:1
>  Failed to load resource: net::ERR_FAILED

One of the more idiotic ideas i get is to read in the HTML into a variable and create a js file with just that variable and then write it dynamically into place.

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

#36198

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 02:14 -0700
Message-ID<b3733195-3e87-4343-bea9-d7db78ea44bb@googlegroups.com>
In reply to#36197
Den torsdag 28 mars 2019 kl. 09:53:45 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 09:19:31 UTC+1 skrev Jonas Thörnvall:
> > Den torsdag 28 mars 2019 kl. 06:26:42 UTC+1 skrev Jonas Thörnvall:
> > > When programming my scripts and matching HTML, i've noticed that with an application sized HTML structure it is quite beneficial for me to break up the script part into a logical structure of script sources that i load from start.
> > > 
> > > However as the complexity groves also the HTML that holds canvas, inputs, outputs also groves with the application. And i can feel the necessity to split up the bulk block of HTML, into logical functional subblocks.
> > > 
> > > I mean why should i have the HTML that deals with editing, animation, setting e.t.c in same block?
> > > 
> > > I thought the way to do it was by split up the HTML block into subblocks, that could be loaded as innerHTML into the mainblock.
> > > 
> > > But my innerHTML subblocks also hold function calls to the main HTML file "outerHTML?", and i now realised i don't know howto call the script invoked in outerHTML block from the innerHTML block.
> > > 
> > > Now someone probably say i should skip HTML and make CSS, but i am really not keen on add complexity that is not necessary. I have some CSS for mouseevent handling, but i do not want any where it is not needed.
> > > 
> > > 
> > > Can i reach the script loaded in outerHTML from the innerHTML loaded page "what is the parameters"? If not what approach should i take to split up the main HTML text block into logical subs.
> > > 
> > > Here is how i load the innerHTML blocks into the outer main block.Not that it matter but the blocks are logical units hidden in buttons.
> > > 
> > > document.getElementById("mousedrum").innerHTML='<object style="min-width:100%; min-height: 300; type="text/html" data="virtkeyb.html"  ></object>';
> > > 
> > > JT
> > 
> > I just tested insert an import link into the HTML   
> > <link rel="import" href="virtKeyb.html" >
> > 
> > Gives me
> > sequenser.html:1 Access to imported resource at 'file:///C:/Users/jonas/Desktop/KOD%20p%C3%A5g%C3%A5ende/27%20Mars/virtKeyb.html' from origin 'null' has been blocked by CORS policy: The response is invalid.
> > virtKeyb.html:1
> >  Failed to load resource: net::ERR_FAILED
> 
> One of the more idiotic ideas i get is to read in the HTML into a variable and create a js file with just that variable and then write it dynamically into place.

It is a bit of proof of the language concept of Javascript that the more idiotic ideas you are able to come up with, the bigger the chance that they actually will work when implemented with javacript. I just removed the linebreaks and paragraphs.

But really should there not be a better way...

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

#36199

FromJulio Di Egidio <julio@diegidio.name>
Date2019-03-28 02:47 -0700
Message-ID<1fc492d9-7e39-47dc-8006-5dedf8957ba8@googlegroups.com>
In reply to#36198
On Thursday, 28 March 2019 10:14:37 UTC+1, Jonas Thörnvall  wrote:

> It is a bit of proof of the language concept of Javascript that the more
> idiotic ideas you are able to come up with, the bigger the chance that
> they actually will work when implemented with javacript.

Sure, we are all learning how competent and successful is your strategy.

> But really should there not be a better way...

Nope, quantum computers are needed to "load html templates with JS"...

Julio

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

#36201

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 03:20 -0700
Message-ID<6a55ae90-383c-4471-ad93-76aaa36c3d0f@googlegroups.com>
In reply to#36199
Den torsdag 28 mars 2019 kl. 10:47:34 UTC+1 skrev Julio Di Egidio:
> On Thursday, 28 March 2019 10:14:37 UTC+1, Jonas Thörnvall  wrote:
> 
> > It is a bit of proof of the language concept of Javascript that the more
> > idiotic ideas you are able to come up with, the bigger the chance that
> > they actually will work when implemented with javacript.
> 
> Sure, we are all learning how competent and successful is your strategy.
> 
> > But really should there not be a better way...
> 
> Nope, quantum computers are needed to "load html templates with JS"...
> 
> Julio

Thanks Julio finally something usefull

https://www.codereadability.com/constructing-html-with-templates/

But a bit late, i ain't fucking going to change it now.

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

#36205

FromJulio Di Egidio <julio@diegidio.name>
Date2019-03-28 04:49 -0700
Message-ID<e186ec31-d11d-4b98-8406-b3a0f62f7557@googlegroups.com>
In reply to#36201
On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:

> Thanks Julio finally something usefull

I try and try, eventually you can suck my socks.  :)

> https://www.codereadability.com/constructing-html-with-templates/

Of all the articles, couldn't you find anything worse than that?

And I mean: besides that it ends up using just libraries, so good riddance
to learning anything at all, but the very idea of HTML (or CSS) hard-coded
into JS is just a NO NO, and good riddance to React and similar upside down
nonsense, too.

Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.

Here is a basic approach where I am loading html fragments (just the html that
you need, not a full page, still give your template an html extension to work
with it in an editor) directly into some DIV or similar:

	function loadTemplate(templateUrl, onSuccess, onError)
	{
		var xhr = new XMLHttpRequest();

		xhr.onload = function ()
		{
			if (xhr.status === 200)
			{
				onSuccess(xhr.responseText);
			}
			else
			{
				onError(xhr.statusText);
			}
		};

		xhr.onerror = function ()
		{
			onError("Network Error");
		};

		xhr.open("GET", templateUrl, true);

		xhr.responseType = "text";

		xhr.send(null);
	}

loadTemplate(templateUrl,
	function (responseText)
	{
		target.innerHTML = responseText;  // target is a DIV

		cont();  // calling a continuation, YMMV
	},
	function (statusText)
	{
		throw new $InvalidTemplateError(statusText);
	});

And now you can really thank me, as that's production-level code, just slightly
abridged for simplicity.

> But a bit late, i ain't fucking going to change it now.

Then another lesson: you will not fix it later, it's now or never...

Have fun,

Julio

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

#36207

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:03 -0700
Message-ID<e0f3a3b5-58de-4869-b193-47869a004da7@googlegroups.com>
In reply to#36205
Den torsdag 28 mars 2019 kl. 12:49:50 UTC+1 skrev Julio Di Egidio:
> On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:
> 
> > Thanks Julio finally something usefull
> 
> I try and try, eventually you can suck my socks.  :)
> 
> > https://www.codereadability.com/constructing-html-with-templates/
> 
> Of all the articles, couldn't you find anything worse than that?
> 
> And I mean: besides that it ends up using just libraries, so good riddance
> to learning anything at all, but the very idea of HTML (or CSS) hard-coded
> into JS is just a NO NO, and good riddance to React and similar upside down
> nonsense, too.
> 
> Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.
> 
> Here is a basic approach where I am loading html fragments (just the html that
> you need, not a full page, still give your template an html extension to work
> with it in an editor) directly into some DIV or similar:
> 
> 	function loadTemplate(templateUrl, onSuccess, onError)
> 	{
> 		var xhr = new XMLHttpRequest();
> 
> 		xhr.onload = function ()
> 		{
> 			if (xhr.status === 200)
> 			{
> 				onSuccess(xhr.responseText);
> 			}
> 			else
> 			{
> 				onError(xhr.statusText);
> 			}
> 		};
> 
> 		xhr.onerror = function ()
> 		{
> 			onError("Network Error");
> 		};
> 
> 		xhr.open("GET", templateUrl, true);
> 
> 		xhr.responseType = "text";
> 
> 		xhr.send(null);
> 	}
> 
> loadTemplate(templateUrl,
> 	function (responseText)
> 	{
> 		target.innerHTML = responseText;  // target is a DIV
> 
> 		cont();  // calling a continuation, YMMV
> 	},
> 	function (statusText)
> 	{
> 		throw new $InvalidTemplateError(statusText);
> 	});
> 
> And now you can really thank me, as that's production-level code, just slightly
> abridged for simplicity.
> 
> > But a bit late, i ain't fucking going to change it now.
> 
> Then another lesson: you will not fix it later, it's now or never...
> 
> Have fun,
> 
> Julio

Very nice Julio, but can i ask you one thing why is those 15 lines of code hiding in an incomprehensible bracket structure needed.

Afterall all we want to do is load a bit of text, are we going to blip-blop this one out of context like all the new Javascript syntax.

Can you give me ****1**** good reason for ****why**** load.SubHTML(URL);
is out of reach for the buttsniffing ENTP's?

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

#36208

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:12 -0700
Message-ID<4174f740-c606-4cfa-ac98-625280b3b1c2@googlegroups.com>
In reply to#36207
Den torsdag 28 mars 2019 kl. 13:03:48 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 12:49:50 UTC+1 skrev Julio Di Egidio:
> > On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:
> > 
> > > Thanks Julio finally something usefull
> > 
> > I try and try, eventually you can suck my socks.  :)
> > 
> > > https://www.codereadability.com/constructing-html-with-templates/
> > 
> > Of all the articles, couldn't you find anything worse than that?
> > 
> > And I mean: besides that it ends up using just libraries, so good riddance
> > to learning anything at all, but the very idea of HTML (or CSS) hard-coded
> > into JS is just a NO NO, and good riddance to React and similar upside down
> > nonsense, too.
> > 
> > Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.
> > 
> > Here is a basic approach where I am loading html fragments (just the html that
> > you need, not a full page, still give your template an html extension to work
> > with it in an editor) directly into some DIV or similar:
> > 
> > 	function loadTemplate(templateUrl, onSuccess, onError)
> > 	{
> > 		var xhr = new XMLHttpRequest();
> > 
> > 		xhr.onload = function ()
> > 		{
> > 			if (xhr.status === 200)
> > 			{
> > 				onSuccess(xhr.responseText);
> > 			}
> > 			else
> > 			{
> > 				onError(xhr.statusText);
> > 			}
> > 		};
> > 
> > 		xhr.onerror = function ()
> > 		{
> > 			onError("Network Error");
> > 		};
> > 
> > 		xhr.open("GET", templateUrl, true);
> > 
> > 		xhr.responseType = "text";
> > 
> > 		xhr.send(null);
> > 	}
> > 
> > loadTemplate(templateUrl,
> > 	function (responseText)
> > 	{
> > 		target.innerHTML = responseText;  // target is a DIV
> > 
> > 		cont();  // calling a continuation, YMMV
> > 	},
> > 	function (statusText)
> > 	{
> > 		throw new $InvalidTemplateError(statusText);
> > 	});
> > 
> > And now you can really thank me, as that's production-level code, just slightly
> > abridged for simplicity.
> > 
> > > But a bit late, i ain't fucking going to change it now.
> > 
> > Then another lesson: you will not fix it later, it's now or never...
> > 
> > Have fun,
> > 
> > Julio
> 
> Very nice Julio, but can i ask you one thing why is those 15 lines of code hiding in an incomprehensible bracket structure needed.
> 
> Afterall all we want to do is load a bit of text, are we going to blip-blop this one out of context like all the new Javascript syntax.
> 
> Can you give me ****1**** good reason for ****why**** load.SubHTML(URL);
> is out of reach for the buttsniffing ENTP's?

I mean it is not even an URL i try to load just a relative textblock for god sake, what the fuck is wrong with the people who implement the language. Yes i now there is an URL behind it when you download, but so it is for any img.

And i have not fucking seen any fullpaths to relative image files.
Maybe this not even an Javascript issue?

This should been done in HTML from start, it need subHTML that can be loaded by "URL" or local path?

I have not seen the need for investigate the network when loading an http://image so i can not see the validity for it loading a textblock.

The more i think about it the more sure i get there is something missing in HTML.

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

#36209

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:13 -0700
Message-ID<f7adbaa1-15de-402a-959a-b48ca24fcf71@googlegroups.com>
In reply to#36208
Den torsdag 28 mars 2019 kl. 13:12:12 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 13:03:48 UTC+1 skrev Jonas Thörnvall:
> > Den torsdag 28 mars 2019 kl. 12:49:50 UTC+1 skrev Julio Di Egidio:
> > > On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:
> > > 
> > > > Thanks Julio finally something usefull
> > > 
> > > I try and try, eventually you can suck my socks.  :)
> > > 
> > > > https://www.codereadability.com/constructing-html-with-templates/
> > > 
> > > Of all the articles, couldn't you find anything worse than that?
> > > 
> > > And I mean: besides that it ends up using just libraries, so good riddance
> > > to learning anything at all, but the very idea of HTML (or CSS) hard-coded
> > > into JS is just a NO NO, and good riddance to React and similar upside down
> > > nonsense, too.
> > > 
> > > Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.
> > > 
> > > Here is a basic approach where I am loading html fragments (just the html that
> > > you need, not a full page, still give your template an html extension to work
> > > with it in an editor) directly into some DIV or similar:
> > > 
> > > 	function loadTemplate(templateUrl, onSuccess, onError)
> > > 	{
> > > 		var xhr = new XMLHttpRequest();
> > > 
> > > 		xhr.onload = function ()
> > > 		{
> > > 			if (xhr.status === 200)
> > > 			{
> > > 				onSuccess(xhr.responseText);
> > > 			}
> > > 			else
> > > 			{
> > > 				onError(xhr.statusText);
> > > 			}
> > > 		};
> > > 
> > > 		xhr.onerror = function ()
> > > 		{
> > > 			onError("Network Error");
> > > 		};
> > > 
> > > 		xhr.open("GET", templateUrl, true);
> > > 
> > > 		xhr.responseType = "text";
> > > 
> > > 		xhr.send(null);
> > > 	}
> > > 
> > > loadTemplate(templateUrl,
> > > 	function (responseText)
> > > 	{
> > > 		target.innerHTML = responseText;  // target is a DIV
> > > 
> > > 		cont();  // calling a continuation, YMMV
> > > 	},
> > > 	function (statusText)
> > > 	{
> > > 		throw new $InvalidTemplateError(statusText);
> > > 	});
> > > 
> > > And now you can really thank me, as that's production-level code, just slightly
> > > abridged for simplicity.
> > > 
> > > > But a bit late, i ain't fucking going to change it now.
> > > 
> > > Then another lesson: you will not fix it later, it's now or never...
> > > 
> > > Have fun,
> > > 
> > > Julio
> > 
> > Very nice Julio, but can i ask you one thing why is those 15 lines of code hiding in an incomprehensible bracket structure needed.
> > 
> > Afterall all we want to do is load a bit of text, are we going to blip-blop this one out of context like all the new Javascript syntax.
> > 
> > Can you give me ****1**** good reason for ****why**** load.SubHTML(URL);
> > is out of reach for the buttsniffing ENTP's?
> 
> I mean it is not even an URL i try to load just a relative textblock for god sake, what the fuck is wrong with the people who implement the language. Yes i now there is an URL behind it when you download, but so it is for any img.
> 
> And i have not fucking seen any fullpaths to relative image files.
> Maybe this not even an Javascript issue?
> 
> This should been done in HTML from start, it need subHTML that can be loaded by "URL" or local path?
> 
> I have not seen the need for investigate the network when loading an http://image so i can not see the validity for it loading a textblock.
> 
> The more i think about it the more sure i get there is something missing in HTML.

<SUBHtml source="URL">Yeah this is where we load it!</SUBHtml>

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

#36210

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:19 -0700
Message-ID<99b20cec-164e-452f-aef0-ffe93207adf1@googlegroups.com>
In reply to#36209
Den torsdag 28 mars 2019 kl. 13:14:04 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 13:12:12 UTC+1 skrev Jonas Thörnvall:
> > Den torsdag 28 mars 2019 kl. 13:03:48 UTC+1 skrev Jonas Thörnvall:
> > > Den torsdag 28 mars 2019 kl. 12:49:50 UTC+1 skrev Julio Di Egidio:
> > > > On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:
> > > > 
> > > > > Thanks Julio finally something usefull
> > > > 
> > > > I try and try, eventually you can suck my socks.  :)
> > > > 
> > > > > https://www.codereadability.com/constructing-html-with-templates/
> > > > 
> > > > Of all the articles, couldn't you find anything worse than that?
> > > > 
> > > > And I mean: besides that it ends up using just libraries, so good riddance
> > > > to learning anything at all, but the very idea of HTML (or CSS) hard-coded
> > > > into JS is just a NO NO, and good riddance to React and similar upside down
> > > > nonsense, too.
> > > > 
> > > > Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.
> > > > 
> > > > Here is a basic approach where I am loading html fragments (just the html that
> > > > you need, not a full page, still give your template an html extension to work
> > > > with it in an editor) directly into some DIV or similar:
> > > > 
> > > > 	function loadTemplate(templateUrl, onSuccess, onError)
> > > > 	{
> > > > 		var xhr = new XMLHttpRequest();
> > > > 
> > > > 		xhr.onload = function ()
> > > > 		{
> > > > 			if (xhr.status === 200)
> > > > 			{
> > > > 				onSuccess(xhr.responseText);
> > > > 			}
> > > > 			else
> > > > 			{
> > > > 				onError(xhr.statusText);
> > > > 			}
> > > > 		};
> > > > 
> > > > 		xhr.onerror = function ()
> > > > 		{
> > > > 			onError("Network Error");
> > > > 		};
> > > > 
> > > > 		xhr.open("GET", templateUrl, true);
> > > > 
> > > > 		xhr.responseType = "text";
> > > > 
> > > > 		xhr.send(null);
> > > > 	}
> > > > 
> > > > loadTemplate(templateUrl,
> > > > 	function (responseText)
> > > > 	{
> > > > 		target.innerHTML = responseText;  // target is a DIV
> > > > 
> > > > 		cont();  // calling a continuation, YMMV
> > > > 	},
> > > > 	function (statusText)
> > > > 	{
> > > > 		throw new $InvalidTemplateError(statusText);
> > > > 	});
> > > > 
> > > > And now you can really thank me, as that's production-level code, just slightly
> > > > abridged for simplicity.
> > > > 
> > > > > But a bit late, i ain't fucking going to change it now.
> > > > 
> > > > Then another lesson: you will not fix it later, it's now or never...
> > > > 
> > > > Have fun,
> > > > 
> > > > Julio
> > > 
> > > Very nice Julio, but can i ask you one thing why is those 15 lines of code hiding in an incomprehensible bracket structure needed.
> > > 
> > > Afterall all we want to do is load a bit of text, are we going to blip-blop this one out of context like all the new Javascript syntax.
> > > 
> > > Can you give me ****1**** good reason for ****why**** load.SubHTML(URL);
> > > is out of reach for the buttsniffing ENTP's?
> > 
> > I mean it is not even an URL i try to load just a relative textblock for god sake, what the fuck is wrong with the people who implement the language. Yes i now there is an URL behind it when you download, but so it is for any img.
> > 
> > And i have not fucking seen any fullpaths to relative image files.
> > Maybe this not even an Javascript issue?
> > 
> > This should been done in HTML from start, it need subHTML that can be loaded by "URL" or local path?
> > 
> > I have not seen the need for investigate the network when loading an http://image so i can not see the validity for it loading a textblock.
> > 
> > The more i think about it the more sure i get there is something missing in HTML.
> 
> <SUBHtml source="URL">Yeah this is where we load it!</SUBHtml>

Oh wait a minute the one who invented HTML had it in mind, ***BUT SOME IDIOT*** DECIDED TO BREAK IT OUT FROM THE HTML PAGE!

<FRAME SRC=""></FRAME>

Who are the fucking idiot now that is an HTML tag, you fucking morons and it is intended to be used in HTML not outside.

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

#36212

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:24 -0700
Message-ID<e982c123-1fd2-40eb-a105-9d376167c2e8@googlegroups.com>
In reply to#36210
Den torsdag 28 mars 2019 kl. 13:20:05 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 13:14:04 UTC+1 skrev Jonas Thörnvall:
> > Den torsdag 28 mars 2019 kl. 13:12:12 UTC+1 skrev Jonas Thörnvall:
> > > Den torsdag 28 mars 2019 kl. 13:03:48 UTC+1 skrev Jonas Thörnvall:
> > > > Den torsdag 28 mars 2019 kl. 12:49:50 UTC+1 skrev Julio Di Egidio:
> > > > > On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:
> > > > > 
> > > > > > Thanks Julio finally something usefull
> > > > > 
> > > > > I try and try, eventually you can suck my socks.  :)
> > > > > 
> > > > > > https://www.codereadability.com/constructing-html-with-templates/
> > > > > 
> > > > > Of all the articles, couldn't you find anything worse than that?
> > > > > 
> > > > > And I mean: besides that it ends up using just libraries, so good riddance
> > > > > to learning anything at all, but the very idea of HTML (or CSS) hard-coded
> > > > > into JS is just a NO NO, and good riddance to React and similar upside down
> > > > > nonsense, too.
> > > > > 
> > > > > Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.
> > > > > 
> > > > > Here is a basic approach where I am loading html fragments (just the html that
> > > > > you need, not a full page, still give your template an html extension to work
> > > > > with it in an editor) directly into some DIV or similar:
> > > > > 
> > > > > 	function loadTemplate(templateUrl, onSuccess, onError)
> > > > > 	{
> > > > > 		var xhr = new XMLHttpRequest();
> > > > > 
> > > > > 		xhr.onload = function ()
> > > > > 		{
> > > > > 			if (xhr.status === 200)
> > > > > 			{
> > > > > 				onSuccess(xhr.responseText);
> > > > > 			}
> > > > > 			else
> > > > > 			{
> > > > > 				onError(xhr.statusText);
> > > > > 			}
> > > > > 		};
> > > > > 
> > > > > 		xhr.onerror = function ()
> > > > > 		{
> > > > > 			onError("Network Error");
> > > > > 		};
> > > > > 
> > > > > 		xhr.open("GET", templateUrl, true);
> > > > > 
> > > > > 		xhr.responseType = "text";
> > > > > 
> > > > > 		xhr.send(null);
> > > > > 	}
> > > > > 
> > > > > loadTemplate(templateUrl,
> > > > > 	function (responseText)
> > > > > 	{
> > > > > 		target.innerHTML = responseText;  // target is a DIV
> > > > > 
> > > > > 		cont();  // calling a continuation, YMMV
> > > > > 	},
> > > > > 	function (statusText)
> > > > > 	{
> > > > > 		throw new $InvalidTemplateError(statusText);
> > > > > 	});
> > > > > 
> > > > > And now you can really thank me, as that's production-level code, just slightly
> > > > > abridged for simplicity.
> > > > > 
> > > > > > But a bit late, i ain't fucking going to change it now.
> > > > > 
> > > > > Then another lesson: you will not fix it later, it's now or never...
> > > > > 
> > > > > Have fun,
> > > > > 
> > > > > Julio
> > > > 
> > > > Very nice Julio, but can i ask you one thing why is those 15 lines of code hiding in an incomprehensible bracket structure needed.
> > > > 
> > > > Afterall all we want to do is load a bit of text, are we going to blip-blop this one out of context like all the new Javascript syntax.
> > > > 
> > > > Can you give me ****1**** good reason for ****why**** load.SubHTML(URL);
> > > > is out of reach for the buttsniffing ENTP's?
> > > 
> > > I mean it is not even an URL i try to load just a relative textblock for god sake, what the fuck is wrong with the people who implement the language. Yes i now there is an URL behind it when you download, but so it is for any img.
> > > 
> > > And i have not fucking seen any fullpaths to relative image files.
> > > Maybe this not even an Javascript issue?
> > > 
> > > This should been done in HTML from start, it need subHTML that can be loaded by "URL" or local path?
> > > 
> > > I have not seen the need for investigate the network when loading an http://image so i can not see the validity for it loading a textblock.
> > > 
> > > The more i think about it the more sure i get there is something missing in HTML.
> > 
> > <SUBHtml source="URL">Yeah this is where we load it!</SUBHtml>
> 
> Oh wait a minute the one who invented HTML had it in mind, ***BUT SOME IDIOT*** DECIDED TO BREAK IT OUT FROM THE HTML PAGE!
> 
> <FRAME SRC=""></FRAME>
> 
> Who are the fucking idiot now that is an HTML tag, you fucking morons and it is intended to be used in HTML not outside.

But probably there was some sniveling little ENTP high on TABLES that decided that FRAME probably also was a structural tag/element, yeah and it kind of was ****BUT INSIDE THE HTML STRUCTURE****.

This is what you get when you put idiot ENTP's to implement ideas.

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

#36214

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:32 -0700
Message-ID<a8a0d4e0-c95e-47fe-9982-f79c69e43a5b@googlegroups.com>
In reply to#36210
Den torsdag 28 mars 2019 kl. 13:20:05 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 13:14:04 UTC+1 skrev Jonas Thörnvall:
> > Den torsdag 28 mars 2019 kl. 13:12:12 UTC+1 skrev Jonas Thörnvall:
> > > Den torsdag 28 mars 2019 kl. 13:03:48 UTC+1 skrev Jonas Thörnvall:
> > > > Den torsdag 28 mars 2019 kl. 12:49:50 UTC+1 skrev Julio Di Egidio:
> > > > > On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:
> > > > > 
> > > > > > Thanks Julio finally something usefull
> > > > > 
> > > > > I try and try, eventually you can suck my socks.  :)
> > > > > 
> > > > > > https://www.codereadability.com/constructing-html-with-templates/
> > > > > 
> > > > > Of all the articles, couldn't you find anything worse than that?
> > > > > 
> > > > > And I mean: besides that it ends up using just libraries, so good riddance
> > > > > to learning anything at all, but the very idea of HTML (or CSS) hard-coded
> > > > > into JS is just a NO NO, and good riddance to React and similar upside down
> > > > > nonsense, too.
> > > > > 
> > > > > Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.
> > > > > 
> > > > > Here is a basic approach where I am loading html fragments (just the html that
> > > > > you need, not a full page, still give your template an html extension to work
> > > > > with it in an editor) directly into some DIV or similar:
> > > > > 
> > > > > 	function loadTemplate(templateUrl, onSuccess, onError)
> > > > > 	{
> > > > > 		var xhr = new XMLHttpRequest();
> > > > > 
> > > > > 		xhr.onload = function ()
> > > > > 		{
> > > > > 			if (xhr.status === 200)
> > > > > 			{
> > > > > 				onSuccess(xhr.responseText);
> > > > > 			}
> > > > > 			else
> > > > > 			{
> > > > > 				onError(xhr.statusText);
> > > > > 			}
> > > > > 		};
> > > > > 
> > > > > 		xhr.onerror = function ()
> > > > > 		{
> > > > > 			onError("Network Error");
> > > > > 		};
> > > > > 
> > > > > 		xhr.open("GET", templateUrl, true);
> > > > > 
> > > > > 		xhr.responseType = "text";
> > > > > 
> > > > > 		xhr.send(null);
> > > > > 	}
> > > > > 
> > > > > loadTemplate(templateUrl,
> > > > > 	function (responseText)
> > > > > 	{
> > > > > 		target.innerHTML = responseText;  // target is a DIV
> > > > > 
> > > > > 		cont();  // calling a continuation, YMMV
> > > > > 	},
> > > > > 	function (statusText)
> > > > > 	{
> > > > > 		throw new $InvalidTemplateError(statusText);
> > > > > 	});
> > > > > 
> > > > > And now you can really thank me, as that's production-level code, just slightly
> > > > > abridged for simplicity.
> > > > > 
> > > > > > But a bit late, i ain't fucking going to change it now.
> > > > > 
> > > > > Then another lesson: you will not fix it later, it's now or never...
> > > > > 
> > > > > Have fun,
> > > > > 
> > > > > Julio
> > > > 
> > > > Very nice Julio, but can i ask you one thing why is those 15 lines of code hiding in an incomprehensible bracket structure needed.
> > > > 
> > > > Afterall all we want to do is load a bit of text, are we going to blip-blop this one out of context like all the new Javascript syntax.
> > > > 
> > > > Can you give me ****1**** good reason for ****why**** load.SubHTML(URL);
> > > > is out of reach for the buttsniffing ENTP's?
> > > 
> > > I mean it is not even an URL i try to load just a relative textblock for god sake, what the fuck is wrong with the people who implement the language. Yes i now there is an URL behind it when you download, but so it is for any img.
> > > 
> > > And i have not fucking seen any fullpaths to relative image files.
> > > Maybe this not even an Javascript issue?
> > > 
> > > This should been done in HTML from start, it need subHTML that can be loaded by "URL" or local path?
> > > 
> > > I have not seen the need for investigate the network when loading an http://image so i can not see the validity for it loading a textblock.
> > > 
> > > The more i think about it the more sure i get there is something missing in HTML.
> > 
> > <SUBHtml source="URL">Yeah this is where we load it!</SUBHtml>
> 
> Oh wait a minute the one who invented HTML had it in mind, ***BUT SOME IDIOT*** DECIDED TO BREAK IT OUT FROM THE HTML PAGE!
> 
> <FRAME SRC=""></FRAME>
> 
> Who are the fucking idiot now that is an HTML tag, you fucking morons and it is intended to be used in HTML not outside.

Now i am smart enough to see your objection that people would use it to publish others pages inside their frames. But you can do that anyway can't you. And it would been easy to just allow local path url if that is really the reason.

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

#36215

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:37 -0700
Message-ID<08754e0a-a385-42aa-a3bd-58349d0a8eda@googlegroups.com>
In reply to#36210
Den torsdag 28 mars 2019 kl. 13:20:05 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 13:14:04 UTC+1 skrev Jonas Thörnvall:
> > Den torsdag 28 mars 2019 kl. 13:12:12 UTC+1 skrev Jonas Thörnvall:
> > > Den torsdag 28 mars 2019 kl. 13:03:48 UTC+1 skrev Jonas Thörnvall:
> > > > Den torsdag 28 mars 2019 kl. 12:49:50 UTC+1 skrev Julio Di Egidio:
> > > > > On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:
> > > > > 
> > > > > > Thanks Julio finally something usefull
> > > > > 
> > > > > I try and try, eventually you can suck my socks.  :)
> > > > > 
> > > > > > https://www.codereadability.com/constructing-html-with-templates/
> > > > > 
> > > > > Of all the articles, couldn't you find anything worse than that?
> > > > > 
> > > > > And I mean: besides that it ends up using just libraries, so good riddance
> > > > > to learning anything at all, but the very idea of HTML (or CSS) hard-coded
> > > > > into JS is just a NO NO, and good riddance to React and similar upside down
> > > > > nonsense, too.
> > > > > 
> > > > > Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.
> > > > > 
> > > > > Here is a basic approach where I am loading html fragments (just the html that
> > > > > you need, not a full page, still give your template an html extension to work
> > > > > with it in an editor) directly into some DIV or similar:
> > > > > 
> > > > > 	function loadTemplate(templateUrl, onSuccess, onError)
> > > > > 	{
> > > > > 		var xhr = new XMLHttpRequest();
> > > > > 
> > > > > 		xhr.onload = function ()
> > > > > 		{
> > > > > 			if (xhr.status === 200)
> > > > > 			{
> > > > > 				onSuccess(xhr.responseText);
> > > > > 			}
> > > > > 			else
> > > > > 			{
> > > > > 				onError(xhr.statusText);
> > > > > 			}
> > > > > 		};
> > > > > 
> > > > > 		xhr.onerror = function ()
> > > > > 		{
> > > > > 			onError("Network Error");
> > > > > 		};
> > > > > 
> > > > > 		xhr.open("GET", templateUrl, true);
> > > > > 
> > > > > 		xhr.responseType = "text";
> > > > > 
> > > > > 		xhr.send(null);
> > > > > 	}
> > > > > 
> > > > > loadTemplate(templateUrl,
> > > > > 	function (responseText)
> > > > > 	{
> > > > > 		target.innerHTML = responseText;  // target is a DIV
> > > > > 
> > > > > 		cont();  // calling a continuation, YMMV
> > > > > 	},
> > > > > 	function (statusText)
> > > > > 	{
> > > > > 		throw new $InvalidTemplateError(statusText);
> > > > > 	});
> > > > > 
> > > > > And now you can really thank me, as that's production-level code, just slightly
> > > > > abridged for simplicity.
> > > > > 
> > > > > > But a bit late, i ain't fucking going to change it now.
> > > > > 
> > > > > Then another lesson: you will not fix it later, it's now or never...
> > > > > 
> > > > > Have fun,
> > > > > 
> > > > > Julio
> > > > 
> > > > Very nice Julio, but can i ask you one thing why is those 15 lines of code hiding in an incomprehensible bracket structure needed.
> > > > 
> > > > Afterall all we want to do is load a bit of text, are we going to blip-blop this one out of context like all the new Javascript syntax.
> > > > 
> > > > Can you give me ****1**** good reason for ****why**** load.SubHTML(URL);
> > > > is out of reach for the buttsniffing ENTP's?
> > > 
> > > I mean it is not even an URL i try to load just a relative textblock for god sake, what the fuck is wrong with the people who implement the language. Yes i now there is an URL behind it when you download, but so it is for any img.
> > > 
> > > And i have not fucking seen any fullpaths to relative image files.
> > > Maybe this not even an Javascript issue?
> > > 
> > > This should been done in HTML from start, it need subHTML that can be loaded by "URL" or local path?
> > > 
> > > I have not seen the need for investigate the network when loading an http://image so i can not see the validity for it loading a textblock.
> > > 
> > > The more i think about it the more sure i get there is something missing in HTML.
> > 
> > <SUBHtml source="URL">Yeah this is where we load it!</SUBHtml>
> 
> Oh wait a minute the one who invented HTML had it in mind, ***BUT SOME IDIOT*** DECIDED TO BREAK IT OUT FROM THE HTML PAGE!
> 
> <FRAME SRC=""></FRAME>
> 
> Who are the fucking idiot now that is an HTML tag, you fucking morons and it is intended to be used in HTML not outside.

You see probably the one who invented the HTML had some insights in publishing using frames, and then they put a poor ENTP idiot onto implement it bwhahahahahh and this is how it ends up.

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

#36216

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:39 -0700
Message-ID<7fa7904f-b7ff-4fc2-8feb-00d6c8153f11@googlegroups.com>
In reply to#36215
Den torsdag 28 mars 2019 kl. 13:38:04 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 13:20:05 UTC+1 skrev Jonas Thörnvall:
> > Den torsdag 28 mars 2019 kl. 13:14:04 UTC+1 skrev Jonas Thörnvall:
> > > Den torsdag 28 mars 2019 kl. 13:12:12 UTC+1 skrev Jonas Thörnvall:
> > > > Den torsdag 28 mars 2019 kl. 13:03:48 UTC+1 skrev Jonas Thörnvall:
> > > > > Den torsdag 28 mars 2019 kl. 12:49:50 UTC+1 skrev Julio Di Egidio:
> > > > > > On Thursday, 28 March 2019 11:20:20 UTC+1, Jonas Thörnvall  wrote:
> > > > > > 
> > > > > > > Thanks Julio finally something usefull
> > > > > > 
> > > > > > I try and try, eventually you can suck my socks.  :)
> > > > > > 
> > > > > > > https://www.codereadability.com/constructing-html-with-templates/
> > > > > > 
> > > > > > Of all the articles, couldn't you find anything worse than that?
> > > > > > 
> > > > > > And I mean: besides that it ends up using just libraries, so good riddance
> > > > > > to learning anything at all, but the very idea of HTML (or CSS) hard-coded
> > > > > > into JS is just a NO NO, and good riddance to React and similar upside down
> > > > > > nonsense, too.
> > > > > > 
> > > > > > Plain JS loading text or XML via AJAX and parsed if needed to HTML, that's it.
> > > > > > 
> > > > > > Here is a basic approach where I am loading html fragments (just the html that
> > > > > > you need, not a full page, still give your template an html extension to work
> > > > > > with it in an editor) directly into some DIV or similar:
> > > > > > 
> > > > > > 	function loadTemplate(templateUrl, onSuccess, onError)
> > > > > > 	{
> > > > > > 		var xhr = new XMLHttpRequest();
> > > > > > 
> > > > > > 		xhr.onload = function ()
> > > > > > 		{
> > > > > > 			if (xhr.status === 200)
> > > > > > 			{
> > > > > > 				onSuccess(xhr.responseText);
> > > > > > 			}
> > > > > > 			else
> > > > > > 			{
> > > > > > 				onError(xhr.statusText);
> > > > > > 			}
> > > > > > 		};
> > > > > > 
> > > > > > 		xhr.onerror = function ()
> > > > > > 		{
> > > > > > 			onError("Network Error");
> > > > > > 		};
> > > > > > 
> > > > > > 		xhr.open("GET", templateUrl, true);
> > > > > > 
> > > > > > 		xhr.responseType = "text";
> > > > > > 
> > > > > > 		xhr.send(null);
> > > > > > 	}
> > > > > > 
> > > > > > loadTemplate(templateUrl,
> > > > > > 	function (responseText)
> > > > > > 	{
> > > > > > 		target.innerHTML = responseText;  // target is a DIV
> > > > > > 
> > > > > > 		cont();  // calling a continuation, YMMV
> > > > > > 	},
> > > > > > 	function (statusText)
> > > > > > 	{
> > > > > > 		throw new $InvalidTemplateError(statusText);
> > > > > > 	});
> > > > > > 
> > > > > > And now you can really thank me, as that's production-level code, just slightly
> > > > > > abridged for simplicity.
> > > > > > 
> > > > > > > But a bit late, i ain't fucking going to change it now.
> > > > > > 
> > > > > > Then another lesson: you will not fix it later, it's now or never...
> > > > > > 
> > > > > > Have fun,
> > > > > > 
> > > > > > Julio
> > > > > 
> > > > > Very nice Julio, but can i ask you one thing why is those 15 lines of code hiding in an incomprehensible bracket structure needed.
> > > > > 
> > > > > Afterall all we want to do is load a bit of text, are we going to blip-blop this one out of context like all the new Javascript syntax.
> > > > > 
> > > > > Can you give me ****1**** good reason for ****why**** load.SubHTML(URL);
> > > > > is out of reach for the buttsniffing ENTP's?
> > > > 
> > > > I mean it is not even an URL i try to load just a relative textblock for god sake, what the fuck is wrong with the people who implement the language. Yes i now there is an URL behind it when you download, but so it is for any img.
> > > > 
> > > > And i have not fucking seen any fullpaths to relative image files.
> > > > Maybe this not even an Javascript issue?
> > > > 
> > > > This should been done in HTML from start, it need subHTML that can be loaded by "URL" or local path?
> > > > 
> > > > I have not seen the need for investigate the network when loading an http://image so i can not see the validity for it loading a textblock.
> > > > 
> > > > The more i think about it the more sure i get there is something missing in HTML.
> > > 
> > > <SUBHtml source="URL">Yeah this is where we load it!</SUBHtml>
> > 
> > Oh wait a minute the one who invented HTML had it in mind, ***BUT SOME IDIOT*** DECIDED TO BREAK IT OUT FROM THE HTML PAGE!
> > 
> > <FRAME SRC=""></FRAME>
> > 
> > Who are the fucking idiot now that is an HTML tag, you fucking morons and it is intended to be used in HTML not outside.
> 
> You see probably the one who invented the HTML had some insights in publishing using frames, and then they put a poor ENTP idiot onto implement it bwhahahahahh and this is how it ends up.

Back to the drawing board W3C it is not to late to change, do it now i know from experience if you do not do it know it will never be done bwhahahahhha

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

#36211

FromJulio Di Egidio <julio@diegidio.name>
Date2019-03-28 05:20 -0700
Message-ID<a3a0c391-1200-4859-a32b-f38a6e6501bd@googlegroups.com>
In reply to#36208
On Thursday, 28 March 2019 13:12:12 UTC+1, Jonas Thörnvall  wrote:

> The more i think about it the more sure i get there is something missing in
> HTML

Yeah, such a pity that you fucking troll aren't on the W3C board, eh...

Julio

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

#36213

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:26 -0700
Message-ID<0c6b3af0-4fa5-47cf-bb8c-7375218d3012@googlegroups.com>
In reply to#36211
Den torsdag 28 mars 2019 kl. 13:21:04 UTC+1 skrev Julio Di Egidio:
> On Thursday, 28 March 2019 13:12:12 UTC+1, Jonas Thörnvall  wrote:
> 
> > The more i think about it the more sure i get there is something missing in
> > HTML
> 
> Yeah, such a pity that you fucking troll aren't on the W3C board, eh...
> 
> Julio

My good a few INTJ's among the ENTP robots on the board would done miracles.

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

#36217

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 05:46 -0700
Message-ID<4f6236f7-0612-495e-852d-36af2360f7dc@googlegroups.com>
In reply to#36211
Den torsdag 28 mars 2019 kl. 13:21:04 UTC+1 skrev Julio Di Egidio:
> On Thursday, 28 March 2019 13:12:12 UTC+1, Jonas Thörnvall  wrote:
> 
> > The more i think about it the more sure i get there is something missing in
> > HTML
> 
> Yeah, such a pity that you fucking troll aren't on the W3C board, eh...
> 
> Julio

Such a pleasure Julio, i did it in two lines, but it would been done in one if it weren't for the idiots, "and even raadable/editable".....

http://midisequenser.000webhostapp.com/

The invoked HTML string variable is inside the NOTES WITH MOUSE & KEYBOARD.

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

#36218

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 06:29 -0700
Message-ID<853aee53-a38b-4622-823d-8b97cff7bd75@googlegroups.com>
In reply to#36217
Den torsdag 28 mars 2019 kl. 13:46:46 UTC+1 skrev Jonas Thörnvall:
> Den torsdag 28 mars 2019 kl. 13:21:04 UTC+1 skrev Julio Di Egidio:
> > On Thursday, 28 March 2019 13:12:12 UTC+1, Jonas Thörnvall  wrote:
> > 
> > > The more i think about it the more sure i get there is something missing in
> > > HTML
> > 
> > Yeah, such a pity that you fucking troll aren't on the W3C board, eh...
> > 
> > Julio
> 
> Such a pleasure Julio, i did it in two lines, but it would been done in one if it weren't for the idiots, "and even raadable/editable".....
> 
> http://midisequenser.000webhostapp.com/
> 
> The invoked HTML string variable is inside the NOTES WITH MOUSE & KEYBOARD.

Do it now Julio it isn't to late to change, if you don't do it now it will never be done. You can to do flies in one swoop, it will correct your flawed ENTP behaviour and correct your missunderstandings about HTML tags  meaning bwahahahahhah

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

#36219

FromJonas Thörnvall <jonas.thornvall@gmail.com>
Date2019-03-28 07:21 -0700
Message-ID<938a9de6-9d83-40f5-8265-4f404c19a216@googlegroups.com>
In reply to#36211
Den torsdag 28 mars 2019 kl. 13:21:04 UTC+1 skrev Julio Di Egidio:
> On Thursday, 28 March 2019 13:12:12 UTC+1, Jonas Thörnvall  wrote:
> 
> > The more i think about it the more sure i get there is something missing in
> > HTML
> 
> Yeah, such a pity that you fucking troll aren't on the W3C board, eh...
> 
> Julio

https://www.youtube.com/watch?v=LY5243pMrq8&feature=share

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

Page 1 of 5  [1] 2 3 4 5  Next page →

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

csiph-web