{"id":19877,"date":"2016-02-01T03:01:01","date_gmt":"2016-01-31T17:01:01","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=19877"},"modified":"2016-01-31T09:50:02","modified_gmt":"2016-01-30T23:50:02","slug":"compound-interest-versus-simple-interest-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/compound-interest-versus-simple-interest-primer-tutorial\/","title":{"rendered":"Compound Interest Versus Simple Interest Primer Tutorial"},"content":{"rendered":"
\"Compound<\/a>

Compound Interest Versus Simple Interest Primer Tutorial<\/p><\/div>\n

Hope you remembered the hares and rabbits<\/a> as we start February with a financial planning web application building on yesterday’s Google Chart Select Event Post Readiness Tutorial<\/a> work.<\/p>\n

So let’s recap (from yesterday) …<\/p>\n

\nThese Google Chart Line\/Bar\/Area\/Column Chart changes involved …
\n … and were done to cater for data POSTed to these charts …
\nWe talk more tomorrow, but you might well choose to POST to these charts as a default method in preference to a GET method as a means to cater for any or all amounts of data needed to be passed in for processing.\n<\/p><\/blockquote>\n

… and so here we are, today, looking at the issue from the viewpoint of the parent part of the parent\/iframe Compound Interest Versus Simple Interest<\/i> web application we have today. With “parent\/iframe” you can think “parent\/child” today. Today the “parent” asks the “child” to do something … as if?!<\/font> That’s it today, but you may recall with the recent Dynamic Pollster<\/i> web application talked about with Google Chart Histogram Chart Select Event Synergy Tutorial<\/a> of recent times, that the “child” (iframed Histogram Chart) was able to send something back to the “parent” via Javascript DOM code like …<\/p>\n


\nvar oblurb=parent.document.getElementById('blurb');
\n\/\/ ...
\n\/\/ ....
\nif (oblurb != null && onego == true) {
\n oblurb.innerHTML=('For ' + colparts[0] + ' ' + postdparts[0].replace(']','') + ' you clicked ' + colparts[1] + ' of ' + postdparts[1].replace(']','') + ' ' + avblurb).replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>').replace(String.fromCharCode(10),'<br>');
\n}
\n<\/code><\/p>\n

… so, these things are possible … but we digress.<\/p>\n

Okay, back at the “parent” asking the “child” to do something … what if it involves memorising the phone book (okay, contact list<\/font>) and then finishing off that web application to make toast for you getting up in the morning before you even knew you wanted toast, all before 4pm? Well, that’s a lot of data, and the GET method that results in a very long URL won’t cut ice for these scenarios for very long. And in today’s Compound Interest Versus Simple Interest<\/i> scenario a lot of data sent to the “child” (iframe) could well occur, depending on what the user of the web application asks of the web application.<\/p>\n

So we POST the data (via an HTML form element target=[iframeID]), and yesterday we got ready for the “child” (iframe) to be able to handle this. Part of being able to handle this is that within the “child” (iframe) Google Charts<\/a> select event<\/a> “haven” for business logic they use, at least for non-mobile platforms, the functionality to …<\/p>\n