{"id":14679,"date":"2015-05-08T05:01:24","date_gmt":"2015-05-07T19:01:24","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=14679"},"modified":"2015-05-07T22:35:53","modified_gmt":"2015-05-07T12:35:53","slug":"htmljavascript-music-follow-up-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/htmljavascript-music-follow-up-tutorial\/","title":{"rendered":"HTML\/Javascript Music Follow Up Tutorial"},"content":{"rendered":"
\"HTML\/Javascript<\/a>

HTML\/Javascript Music Follow Up Tutorial<\/p><\/div>\n

We follow up on our HTML\/Javascript Music Primer Tutorial<\/a> as shown below, today, by setting our minds to a “first draft” of a method to construct a tune in MIDI … say “first draft” because, it is often easier on a “first draft” to involve GET parameters with a URL, for ease of testing. This idea is a “first draft” because there are limits with URL lengths allowable this way, and in order to get around more involved examples than today’s first few bars of F\u00fcr Elise (by Beethoven), we’ll need a subsequent draft that caters for POST parameters involving, perhaps, an HTML form and maybe calling on server-side PHP work … we’ll have to see.<\/p>\n

So what can get sorted out with this “first draft” idea? How about sorting out an internal protocol of communication of data? This type of decision is a hugely important part of the design phases of a project. We’ve opted for …<\/p>\n