{"id":14705,"date":"2015-05-09T05:01:10","date_gmt":"2015-05-08T19:01:10","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=14705"},"modified":"2015-05-08T17:58:26","modified_gmt":"2015-05-08T07:58:26","slug":"htmljavascriptphp-compose-music-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/htmljavascriptphp-compose-music-tutorial\/","title":{"rendered":"HTML\/Javascript\/PHP Compose Music Tutorial"},"content":{"rendered":"
\"HTML\/Javascript\/PHP<\/a>

HTML\/Javascript\/PHP Compose Music Tutorial<\/p><\/div>\n

Yesterday we set up the MIDI music web application we’ve been working on to take the first steps with composing, with HTML\/Javascript Music Follow Up Tutorial<\/a> as shown below, and as you may recall from this the idea that the GET method would cause URLs that are too long for the web browser with any length to your musical composition, and that we’d have to involve the POST method on an HTML form element, perhaps feeding this through to a server-side language like PHP … well, it panned out this involvement of PHP and HTML forms was overkill for “playing” these long pieces … for that we could resort to “hidden” input text fields … but … yes, there’s always a but … when we got to wanting to be able to save our compositions, and come back to them for playing or tweaking, or both, we could not avoid the use of a server-side language (for us, this is PHP) and the interface to that server-side language, an HTML form element … basically because how else are you going to be able to save the composition to a file, and then reread that file? You need a language like PHP.<\/p>\n

So, here we are, still needing to calibrate the Italian speed words methinks, but otherwise, now, we can (on laptops only, it looks like) …<\/p>\n