{"id":16544,"date":"2015-08-12T05:01:11","date_gmt":"2015-08-11T19:01:11","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=16544"},"modified":"2015-08-11T20:08:06","modified_gmt":"2015-08-11T10:08:06","slug":"slideshow-animation-via-image-visibility-modelling-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/slideshow-animation-via-image-visibility-modelling-tutorial\/","title":{"rendered":"Slideshow Animation via Image Visibility Modelling Tutorial"},"content":{"rendered":"
\"Slideshow<\/a>

Slideshow Animation via Image Visibility Modelling Tutorial<\/p><\/div>\n

Yesterday, with Slideshow Animation via Image Visibility Follow Up Tutorial<\/a> as shown below, we continued our pictorial, and where possible, textual, synopsis of blog postings … an encapsulation, should we say, presented in the form of a slideshow, where we introduced an HTML form<\/a> element into the mix, which facilitates navigation to other blog postings, where those blog posting are examined via the PHP $_GET[] parameters posted to itself, scrutinising the relevant blog posting for its image-related data.<\/p>\n

Today’s coding of this current project brought issues of “genericity” to the fore. As programmers we often strive for genericity with our work. After all, once you put in all the hours on a piece of software, it can be a bit of a letdown if it applies to too small a set of circumstances or user usage. On the flipside, though, to obsess about genericity can be a good aim, but should stop at a certain point, because, no matter how well you do with it, it can be argued by someone, somewhere, that it doesn’t measure up. Think of the “language” requirements for instance. Think of, “will it work with no electricity” for instance. So obsessing overly, is a waste of angst, but if you don’t care either, it makes for a lazy approach to programming, which will not be noticed with the narrow scope of your endeavours.<\/p>\n

“Genericity” obviously helps explain code to the next person, who perhaps won’t have to do a thing, but you can also “model” a solution and make it pretty obvious what modelling assumptions you’ve made. Our big issue with “genericity” in our current endeavour is how to pin down how image-related data could be represented in a “genericist’s head” in …<\/p>\n

    \n
  1. any web page<\/strike> … too ambitious … so …<\/li>\n
  2. any blog page<\/strike> … too many blog “brands” … so …<\/li>\n
  3. any WordPress blog posting<\/strike> … getting closer, but too many WordPress themes … so …<\/li>\n
  4. any<\/strike> WordPress Twenty Ten theme blog posting … let’s say … and we’ll do the “modelling” for what happens here at this blog to point following programmers into the right direction to make modifications<\/li>\n<\/ol>\n

    … as a personal observation find the most useful “leads” to a “modelling” scenario, are global variables up the top of the code (and it doesn’t have to be too many, even … just something “to hang your hat on”), and comments at the top of the code … nothing more … you should be able to “remodel” with just these cues, we figure. Take a look at slideshow_via_invisibility_and_fade.php<\/a> and hope you understand enough to rework it for your own purposes.<\/p>\n

    Okay, today we tackled that thorny issue to do with image-related data “extraction” from the contents of a WordPress TwentyTen theme blog posting (here at this blog … but reworkable for others, we feel sure) We identified four scenarios …<\/p>\n

      \n
    1. <a …><\/a> tag href to an internal slideshow HTML file<\/li>\n
    2. Twirling Javascript onmouseover scenario … use eval<\/a>([PHPequivalentOfJavascript]) to derive next image name (until, and excluding when, we get back to first image name)<\/li>\n
    3. Single image scenario … and …<\/li>\n
    4. Image place specified that has <td> … <\/td> encasing <ing … \/> and any relevant displayable text (comment) wording<\/li>\n<\/ol>\n

      You can see our progression for yourself with the PHP source code you could call slideshow_via_invisibility_and_fade.php<\/a> which changed from yesterday as per this link<\/a>, or try a live run<\/a>.<\/p>\n

      \n

      Previous relevant Slideshow Animation via Image Visibility Follow Up Tutorial<\/a> is shown below.<\/p>\n

      \"Slideshow<\/a>

      Slideshow Animation via Image Visibility Follow Up Tutorial<\/p><\/div>\n

      We continue on with yesterday’s tutorial Slideshow Animation via Image Visibility Primer Tutorial<\/a> which extended the “overlay” idea presented previously with WordPress Blog Search Within Search Overlay Tutorial<\/a> where, you might remember, we had three HTML elements, one visible and the rest invisible, and we “overlayed” (in quotes, because the technique does not need the CSS “position:absolute”<\/a> property to work) by changing which one was visible at any given time (and at any given time, only one is visible).<\/p>\n

      Yesterday’s work had a hard coded feel to it, and today we widen the scope out a bit more to be generic enough to handle other blog postings, here at this blog, with a pictorial, and where possible, textual, synopsis of the blog posting … an encapsulation, should we say, presented in the form of a slideshow. We cater for this genericity by introducing an HTML form<\/a> element into the mix, which facilitates navigation to other blog postings, where those blog posting are examined via the PHP $_GET[] parameters posted to itself, scrutinising the relevant blog posting for its image-related data. For each blog posting, this can take on a different “guise” and so this is the greatest challenge with this project.<\/p>\n

      As well, regarding yesterday’s work … the HTML meter<\/a> element is not supported with Internet Explorer, nor mobile platforms, so let’s substitute in an HTML input type=number element instead.<\/p>\n

      Another matter of interest is the way we have the wording to accompany the images sit within an HTML div<\/a> element within a table cell (HTML td<\/a> element) so that it justifies to the bottom of the table cell, achieved via the bold<\/b> CSS bits …<\/p>\n


      \n<td id='twording' style=' background-color: #f0f0f0; display: table-cell; vertical-align: bottom;<\/b>'>
      \n<\/code><\/p>\n

      We wanted to thank this link<\/a> heaps, for advice, here.<\/p>\n

      There’s more to do, but isn’t there just about always. You can see our progression for yourself with the PHP source code you could call slideshow_via_invisibility_and_fade.php<\/a> which changed from yesterday as per this link<\/a>, or try a live run<\/a> … believe me, it is better than a dead run.<\/p>\n

      \n

      Previous relevant Slideshow Animation via Image Visibility Primer Tutorial<\/a> is shown below.<\/p>\n

      \"Slideshow<\/a>

      Slideshow Animation via Image Visibility Primer Tutorial<\/p><\/div>\n

      Today’s tutorial extends the “overlay” idea presented yesterday with WordPress Blog Search Within Search Overlay Tutorial<\/a> where, you might remember, we had three HTML elements, one visible and the rest invisible, and we “overlayed” (in quotes, because the technique does not need the CSS “position:absolute”<\/a> property to work) by changing which one was visible at any given time (and at any given time, only one is visible).<\/p>\n

      Today’s tutorial takes the image data from Developing Black and White Photos Primer Tutorial<\/a> as a good candidate to use with PHP’s glob()<\/a> method we discussed last when we presented PHP Modularization for Lighthouses in Australia Tutorial<\/a>.<\/p>\n

      The images of this tutorial are “relatively” stacked into a table cell and take their turns at being the visible one to create the slideshow animation feel to our resultant presentation<\/a>.<\/p>\n

      Some other concepts we’ve visited today with PHP source code you could call slideshow_via_invisibility_and_fade.php<\/a> are …<\/p>\n