{"id":21184,"date":"2016-04-11T03:01:27","date_gmt":"2016-04-10T17:01:27","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=21184"},"modified":"2016-06-03T10:08:42","modified_gmt":"2016-06-03T00:08:42","slug":"feedback-email-attachment-iframe-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/feedback-email-attachment-iframe-tutorial\/","title":{"rendered":"Feedback Email Attachment Iframe Tutorial"},"content":{"rendered":"
\"Feedback<\/a>

Feedback Email Attachment Iframe Tutorial<\/p><\/div>\n

We’re continuing on with our Feedback project for the RJM Programming website today, incorporating the recent Annotation and Email Attachment functionality we last talked about with Canvas Annotation Email Attachment Rotation Tutorial<\/a>. We build on yesterday’s Feedback Email Attachment Primer Tutorial<\/a> as shown below, to add …<\/p>\n

    \n
  1. a dropdown list of RJM Programming Blog Posting Titles to “start the ball rolling” regarding a possible feedback topic for the user<\/li>\n
  2. improvements to styling and practicalities such as supplying default From field to encourage that field’s use by the user<\/li>\n<\/ol>\n

    We use what we like to term as “Client Pre-emptive Iframe” methods to satisfy idea 1 above and maybe you would like to read Client Pre-emptive Iframe Crontab Curl Rotated Report Tutorial<\/a> (all the way through) for a more thorough discussion, but for now, consider the idea as Javascript client work feeling a bit like PHP server work, by using the onload<\/i><\/a> event of an HTML iframe<\/a> element (probably using a src=<\/i> parameter from the same domain your HTML sits on) to (what feels like internally datascraping) the iframe’s document.body.innerHTML<\/i> and extract something of interest to load into a local HTML element, quite often that being an HTML div element. We do that to take that dropdown of the RJM Programming landing page relating to the latest RJM Programming blog postings and “slap” this into the local HTML div element, and rewrite the logic of its onchange<\/i> event logic to do what we want to do here, rather than what the RJM Programming landing page wants to do. In doing this, our Javascript client is actually “channelling” PHP behind the scenes, else how else could we glean that information from a WordPress MySql database (pray tell … have been longing for a chance to use that phrase<\/font>)? Read that previous link’s blog posting, and perhaps more off it to get the whole story of how HTML can be the “conduit” of doing server side feeling things via the use of the dynamic duo … Crontab (of Linux or Unix) and Curl (of lots of platforms).<\/p>\n

    This is “Client Pre-emptive Iframe” where we know the src=<\/i> of the HTML iframe in a “static” way, but we believe here that some web applications can be designed where src=<\/i> can be in the form of a sequence that doesn’t always exist, but your code can check for this, and not fall over, and continue being that little bit “server” like without being “server” like … “Clayton’s”<\/i><\/a> anyone?!<\/p>\n

    So, again, please see …<\/p>\n