{"id":46721,"date":"2019-10-10T03:01:54","date_gmt":"2019-10-09T17:01:54","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=46721"},"modified":"2019-10-09T09:43:03","modified_gmt":"2019-10-08T23:43:03","slug":"inhouse-slideshow-design-exif-order-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/inhouse-slideshow-design-exif-order-tutorial\/","title":{"rendered":"Inhouse Slideshow Design Exif Order Tutorial"},"content":{"rendered":"
\"Inhouse<\/a>

Inhouse Slideshow Design Exif Order Tutorial<\/p><\/div>\n

Ever get those “oops” moments? <\/p>\n

Anyone, anyone<\/a>? … no, Reverend William Archibald Spooner<\/a> … we will not accept that answer here now, thank you very much.<\/p><\/blockquote>\n

Ever get an “oops” moment that you can wait for a little while before resolving? … <\/p>\n

No, William Archibald, history does not always repeat, and may we reiterate … no, William Archibald, history does not always repeat … that’s right … history does not always burp<\/strike>repeat.<\/p><\/blockquote>\n

Well, we got one regarding our Inhouse Slideshow reworkings. You see, though we automated, as with many automation thoughts, there is a chance some nuances don’t come across with translation (of concept). In the “old days” of this concept we’d manually put together HTML that involved a table with a single row (tr) element containing multiple (horizontal scrolling) cells (td elements) in an order of our choosing. What we have forsaken, if you will, with our automation, is the absolute control of that ordering process …in short hand …<\/p>\n


\nwe've automated into PHP glob()<\/a> usage, a piece of mind \"ordering of a moment\"
\n<\/code><\/p>\n

… that latter method involving screen captures placed via Mac Paintbrush into slideshow slide images, and often realizing we’d missed something, and going back to infill or jump forward with image file naming with regards to its numerical uniquifiers.<\/p>\n

We’d left poor old “glob” to rescramble what we’d been thinking, order wise, regarding the slideshow slide presentation order. This is too much to ask of poor old “glob” which orders by default via an alphabetical sort. Truth be told, having lost track of the original HTML efforts of the past, now, this is too much to ask of any software component. However, we can reduce the “automation error rate” of poor old “glob” (alone) by helping it out with good ‘ol natsort<\/a> …<\/p>\n

\nnatsort \u2014 Sort an array using a “natural order” algorithm\n<\/p><\/blockquote>\n

… which would reorder a “glob” alphabetic sort order like …<\/p>\n


\nWord_Web_Primer-0of.jpg Word_Web_Primer-10of.jpg Word_Web_Primer-11of.jpg Word_Web_Primer-1of.jpg Word_Web_Primer-2of.jpg Word_Web_Primer-3of.jpg Word_Web_Primer-4of.jpg Word_Web_Primer-5of.jpg Word_Web_Primer-6of.jpg Word_Web_Primer-7of.jpg Word_Web_Primer-8of.jpg Word_Web_Primer-9of.jpg
\n<\/code><\/p>\n

… into a “natsort” order like …<\/p>\n


\nWord_Web_Primer-0of.jpg Word_Web_Primer-1of.jpg Word_Web_Primer-2of.jpg Word_Web_Primer-3of.jpg Word_Web_Primer-4of.jpg Word_Web_Primer-5of.jpg Word_Web_Primer-6of.jpg Word_Web_Primer-7of.jpg Word_Web_Primer-8of.jpg Word_Web_Primer-9of.jpg Word_Web_Primer-10of.jpg Word_Web_Primer-11of.jpg
\n<\/code><\/p>\n

… which, we know (within ourselves<\/a>) matches better the line ————— of our thinking. See, _______________<\/strike>—————. Thanks to this useful link<\/a> for the natsort() usage ideas here.<\/p>\n

Unit testing completed, the deployment, again, matches those ideas of the recent Inhouse Slideshow Design Exif Zip Tutorial<\/a> … in that …<\/p>\n