{"id":62992,"date":"2024-03-15T03:01:42","date_gmt":"2024-03-14T17:01:42","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=62992"},"modified":"2024-03-14T16:11:00","modified_gmt":"2024-03-14T06:11:00","slug":"linked-sentence-story-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/linked-sentence-story-primer-tutorial\/","title":{"rendered":"Linked Sentence Story Primer Tutorial"},"content":{"rendered":"
\"Linked<\/a>

Linked Sentence Story Primer Tutorial<\/p><\/div>\n

We don’t know what amazes you … doh<\/font>! But we get amazed by web application “kludges” that end up working … well, you had to be there<\/font>! Let me explain! In yesterday’s Google Geo Chart and Map Chart Hashtag SMS Tutorial<\/a> … assuming …<\/p>\n

    \n
  1. you were aware of it …<\/li>\n
  2. you visited it …<\/li>\n
  3. your eyes were not glazed over …<\/li>\n
  4. a pet was not barfing on the floor (or elsewhere)<\/font> … at the crucial time when … doopy doopy doop doop, doop doop doop, doop doop doop doop, doopy doopy doop doop …<\/font><\/li>\n
  5. there it was … what?!<\/font> … I’m about to tell you …
    \n…
    \n.
    \n..
    \n….
    \n.
    \n……..
    \n..
    \n…—…
    \n—…— … huh?! …
    \n…
    \n……..
    \n.
    \n…. the codeline …<\/p>\n

    \n document.getElementById(‘remail’).innerHTML=’&#128231;<\/a> ‘ + inplace.split(‘>’)[0] + ‘>&#128223;’;\n<\/p><\/blockquote>\n

    … (unassumingly 9px but, still …)<\/font> gleaming, in the morning’s first rays, within the safety of its code<\/i> element …
    \n … what?!<\/font> … I’m about to tell you …
    \n…
    \n.
    \n..
    \n….
    \n.
    \n……..
    \n..
    \n…—…
    \n—…— … huh?! …
    \n…
    \n……..
    \n.
    \n … “the kludge” … and not just any old “    Clayton’s<\/a> Kludge” (sorry, you’re too late … we’ve patented it already)<\/font> …\n<\/li>\n<\/ol>\n

    Yes, regarding Javascript DOM thinking, we still usually encase a “display:inline” type of scenario in an all encompassing div or span before the contemplation of appending content. But the implication of this codeline is that for the HTML example …<\/p>\n\n\n
    \n
    \n<a id=\"remail\" href=\"mailto:blah\" title=\"First a element\">Email link ... This is roughly the wording of our \"a\" link<\/a>
    \n<\/code><\/td>\n    		 \/\/ looking like
    Email link … This is roughly the wording of our “a” link<\/a><\/td>\n<\/tr>\n<\/table>\n


    \n document.getElementById('remail').innerHTML='&#128231;<\/a> ' + inplace.split('>')[0] + '>&#128223;';
    \n<\/code><\/p>\n

    … could cause one “a” element to be spliced into two … and become …<\/p>\n\n\n
    \n
    \n<a id=\"remail\" href=\"mailto:blah\" title=\"First a element\">&#128231;>\/a> <\/a><a id=\"rsms\" href=\"sms:blah\">&#128223;<\/a>
    \n<\/code><\/td>\n    		 \/\/ looking like
    📧<\/a> <\/a>📟<\/a><\/td>\n<\/tr>\n<\/table>\n

    … without using any overseeing nesting element of any sort!<\/p>\n

    Anyway, we were gobsmacked, and today we write a proof of concept Linked Sentence web application making heavy use of this principle.<\/p>\n

    We thought with this Linked Sentence it could be like a “piecing together” of a story type of thing, with some similarities to the web application of Fairy Story Chrome Dictation Punctuation Tutorial<\/a> times, with this first draft<\/a> Linked Sentence Creator<\/a> web application also “playable” below …<\/p>\n