{"id":35647,"date":"2018-01-24T03:01:38","date_gmt":"2018-01-23T17:01:38","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=35647"},"modified":"2018-01-24T20:27:15","modified_gmt":"2018-01-24T10:27:15","slug":"interesting-places-sorting-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/interesting-places-sorting-tutorial\/","title":{"rendered":"Interesting Places Sorting Tutorial"},"content":{"rendered":"
\"Interesting<\/a>

Interesting Places Sorting Tutorial<\/p><\/div>\n

We’re all different regarding our levels of tolerance for “disorder”. One person’s view of “disorder” is not likely to match, exactly, anybody else within “cooooooeeeeee”. Personally, don’t mind mess, but can disappoint on those occasions where it takes that little bit longer to find something, as was definitely the case leaving yesterday’s Interesting Places Primer Tutorial<\/a>‘s version of our new “Interesting Place” (HTML\/Javascript\/CSS) web application we’ve been working on lately. The reason for the “disorder” inherent in that web application’s HTML select (dropdown) element’s workings is because the source of the data (thanks to The Earth from the Air<\/i> by Yann Arthus-Bertrand (ISBN: 9780500544846)) took a hard copy form. Barring “scanning” processes into character data (yoo hoo Textarea Pointing Local Font Canvas Overlay Deletes Tutorial<\/a> “top” of blog posting thread … with relevant “bottom” “primer” initial premise) it’s most likely going to be a two step process of …<\/p>\n

    \n
  1. collect the geographical latitude and longitude from hard copy (in whatever order it appears in book) onto more hard copy, or to soft copy file perhaps … and transfer this information into (the inherent order of) the HTML select<\/a> (dropdown) element’s option tags … and then, as a separate exercise, because this is not a very orderly way to organize the data …<\/li>\n
  2. allow the software to sort this data into various “views” of that same basic (still “disordered”) data<\/li>\n<\/ol>\n

    You’ll see this “view” way of looking at things permeates the database world too. The underlying data in a database can be collected in quite a “disorderly” way, but define a database “view” of it sorted (or indexed) via the use of database key columns, and that same “disorderly” pig’s ear (no sows were harmed making this blog posting<\/font>) can look like a “silk purse” (no silks were harmed making this blog posting<\/font>).<\/p>\n

    Our web application is not using anything serverside, so we choose to do this job using, respectively …<\/p>\n

      \n
    1. one Javascript Array<\/a> containing (comma separated) latitude,longitude,placename<\/i> … and here, today, to introduce some order …<\/li>\n
    2. six new Javascript Array<\/a>s still containing (comma separated) latitude,longitude,placename<\/i> in orders reflecting the “view” requirements for …\n