{"id":20485,"date":"2016-03-05T03:01:36","date_gmt":"2016-03-04T17:01:36","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=20485"},"modified":"2016-03-04T22:51:07","modified_gmt":"2016-03-04T12:51:07","slug":"inter-web-application-communication-tool-iframe-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/inter-web-application-communication-tool-iframe-tutorial\/","title":{"rendered":"Inter Web Application Communication Tool Iframe Tutorial"},"content":{"rendered":"
\"Inter<\/a>

Inter Web Application Communication Tool Iframe Tutorial<\/p><\/div>\n

Yesterday’s work of Inter Web Application Communication Tool Primer Tutorial<\/a> below was all fine and good regarding a start to the use of …<\/p>\n


\ntop<\/a>.document.title<\/a>
\n<\/code><\/p>\n

… and our “messaging” conduit between web applications that took on the form, in our case, of one parent web application housing several HTML iframe child web application processes referencing the same HTML and Javascript software. That first “draft” felt a bit “supervisory” heavy, so today we grow some awareness of the HTML iframe web applications to their siblings, via the help of top.document.title<\/i> … our unifier.<\/p>\n

You might get a kick out of a couple of new dropdown options …<\/p>\n

    \n
  1. Start the Ball Rolling<\/li>\n
  2. Start the Ball Rolling (Name Prompting)<\/li>\n<\/ol>\n

    … we add today feeling like “kludgy” “artificial intelligence”. We add our “artificial intelligence” functionality just to orchestrate a question from one of your conversationalists, to another of the conversationalists, to get the ball rolling, so to speak.<\/p>\n

    At this start point, of a question, on these new dropdown options, we control the processing by disallowing sibling HTML iframe input type=text interactions for those conversationalists who weren’t last referenced.<\/p>\n

    And how do you suppose we know, as a sibling whether we were last referenced? The last characters of top.document.title<\/i> are scrutinised so that if one of …<\/p>\n

      \n
    1. , [SiblingName]?<\/li>\n
    2. , [SiblingName].<\/li>\n<\/ol>\n

      … is at the end of top.document.title<\/i>, respectively …<\/p>\n

        \n
      1. [SiblingName] only is then allowed to enter the next conversation part, and is forced to answer to the other [SiblingName] they received the message from (and a ? prefix off the first question as that conversationalist’s answer causes the web application to slap in its default answer to the question … and for this bit of logic we’d like to thank this link<\/a> helping with Javascript associative array ideas and the often used Javascript eval<\/a> method we often use at this blog) … or …<\/li>\n
      2. [SiblingName] only is then allowed to enter the next conversation part<\/li>\n<\/ol>\n

        We do this with our recently popular Javascript keyboard events onkeyup<\/i><\/a> and onkeydown<\/i><\/a> to enforce any such restrictions, which, by the way, after the initial “artificial intelligence” starting phase, a conversationalist can reintroduce by ending their conversation part in one of the appropriate “fashions” talked about above.<\/p>\n

        And so you can see the HTML and Javascript source code you could call onion4co_chalkboard.html<\/a> (with its live run<\/a> and its changes from yesterday as per this link<\/a>).<\/p>\n

        \n

        Previous relevant Inter Web Application Communication Tool Primer Tutorial<\/a> is shown below.<\/p>\n

        \"Inter<\/a>

        Inter Web Application Communication Tool Primer Tutorial<\/p><\/div>\n

        Today we start on a series of ideas making use of a new inter web application<\/i> tool. Well, it’s “new” in the sense that we haven’t concentrated on it here at this blog, as of yet.<\/p>\n

        This new conduit of inter web application<\/i> is not rocket science … it is the use of …<\/p>\n


        \n        top<\/a>.document.title<\/a>
        \n<\/code><\/p>\n

        … da da da da!!<\/p>\n

        We place this, at the very least, with …<\/p>\n