{"id":36585,"date":"2018-03-05T03:01:42","date_gmt":"2018-03-04T17:01:42","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=36585"},"modified":"2018-03-04T17:54:56","modified_gmt":"2018-03-04T07:54:56","slug":"blog-kaleidoscopic-view-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/blog-kaleidoscopic-view-primer-tutorial\/","title":{"rendered":"Blog Kaleidoscopic View Primer Tutorial"},"content":{"rendered":"
\"Blog<\/a>

Blog Kaleidoscopic View Primer Tutorial<\/p><\/div>\n

We go to quite a bit of effort writing the wording of the blog posts, not to be noticed a great deal, but, the images we concoct perhaps grab more attention with the search engines. With this in mind, and because we have this imagining of a “kaleidoscope” of imagery related to this blog, mainly, we guess, we’ve put together an HTML and Javascript and CSS web application to show a changing slideshow getting towards a “kaleidoscopic” image view of this blog.<\/p>\n

This web application’s innards, intrinsically very simple, consist, data wise, of one array of image URL members of the (syntax) form …<\/p>\n


\n{absoluteImageURL}[?p={cutToTheChaseURL}&w={blogPostURL}#{blogPostTitleNoBlanks}]
\n<\/code><\/p>\n

Have you ever thought to use ? and & URL arguments (and # hashtag) on an image URL (in the web browser address bar, or programmatically)? We’ve done it before, and there is no trouble about this type of URL showing the image, plus there’s a good chance you’ll make sure caching does not get in the way of seeing that image as it really is then and there. Interesting, huh? Of course, we claim this erudite thought pattern, but our motivation, as ever, is to keep the data arrangements as simple as possible, the above “delimitation” inhouse rules ensuring we can stick with a one array (of single dimension) data arrangement with our work.<\/p>\n

As you try the live run<\/a> and perhaps peruse the HTML and Javascript and CSS rjmgoogleimages.html<\/a> code, you can see that the bulk of the work is the compilation of this array. So how was it derived?<\/p>\n

Via the View Page Source of the Google Advanced Option Image Search URL …<\/p>\n


\nhttps:\/\/www.google.com.au\/search?as_st=y&tbm=isch&hl=en&as_q=rjmprogramming&as_epq=&as_oq=&as_eq=&imgsz=&imgar=&imgc=&imgcolor=&imgtype=&cr=&as_sitesearch=rjmprogramming.com.au&safe=images&as_filetype=&as_rights=<\/a>
\n<\/code><\/p>\n

Thanks, Google<\/a>, for that “view from above” perspective.<\/p>\n

If this was interesting you may be interested in this<\/a> too.<\/p>\n