Before we got sidetracked, but along the same “where of life” themes, before the latest recent web application predilections …
… we were delving into passing on work from the Google Chart‘s Map Chart to the Google Chart Geo Chart and Image Chart Map Chart more often, where we started that thread (at Google Chart Image Chart Map Chart Mainstream Primer Tutorial at the end of last year) with a three point plan (which became four point two days later) …
- Help itself … map.php … phase 1
- Redirect to Image Chart Map Chart … map.php and/or geo_chart.php … just after first prompt … phase 2
- Caller form method=POST map.php action interventions at onsubmit event … non map.php … phase 3
- Transfer the onclick prompt window functionality over to geo_chart.php … phase 4
And then yesterday’s work in Earth Bearing Distance Missing Two Earth Scanner Integration Tutorial involving the Missing Two web application’s interfacing to the Google Chart Map Chart saw a more happy interfacing with this Map Chart, and reminding us with both …
- Google Charts Map Chart
- Google Charts Geo Chart
… how on occasions we could have large data set scenarios relying on PHP $_POST data (via form method=POST (or you can use Ajax FormData post) arrangements) that had not passed on their data parts when the user clicked the “Email” link down the bottom. But ever since that happy discovery from around about the time of Earth Scanner Sharing Itinerary Detail Tutorial that …
- hashtagging … was the friend of …
- “a” “mailto:” and/or “sms:” link hrefs … replacing the need for …
- PHP mail via a local mail server methodologies … when the email body is a single link whose length was greater than about 850 (ie. no such stringent limitations with “just clientside” hashtagging (which we’re yet to know what the limit is, but it seems huge))
… and … spoiler alert … we could not break (where we do not count as broken the clicking of a “Message clipped” message link, which we always click to fully show the whole link, as a warning from your email client application (eg. Gmail)) it with any large amounts of data from our PHP Wikipedia Australian List Integration Tutorial “peer to peer” suite of linked PHP web applications passing large amounts of data to those Google Charts and emailing that on to an emailee recipient. Good news indeed!
The changes feature …
Collect a method=POST (perhaps large data set) into a potentially useful (later) PHP variable hashtag part to an “a” “mailto:” href … |
---|
<?php
?> |
Up the top of where PHP is writing out the Javascript, checking for an email derived URL with huge hashtag we turn into a form method=POST scenario for the user clicking the email body huge link ... |
|
All location.search. strings become, for example ... |
<?php echo "
"; ?> |
Javascript functions that are wrappers to Javascript prompt window scenarios need ... |
<?php echo "
"; ?> |
New if for code involving no data passed in $_GET[] nor $_POST[] but huge hashtag (via email) ... |
<?php
?> |
New Javascript function helpers ... |
<?php echo "
"; ?> |
Add hashtag suffix to "a" "mailto:" link href attribute as applicable ... |
<?php
?> |
Codewise ...
- we changed map.php Map Chart interfacer ...
- we changed gchartgen.js external Javascript ... called by ...
- we changed geo_chart.php Geo Chart interfacer
If this was interesting you may be interested in this too.