Google map in 5.6

Permalink
I upgraded one of our sites to 5.6 and noticed that the Google map block has been changed so that it generates the javascript needed for map in the on_page_view() function and adds it to footer. I'd like to know what is the point of moving the js there?

I do realize that the footer is kind of "ideal" or elegant place to put the js, but it makes creating custom templates for the map more complicated. What I mean is that if my client wants to have a static marker on the map, I could easily add it to custom template in 2 minutes. However, now the same would require overriding the controller (or at least the on_page_view() function) which would eventually generate more problems if someone likes to have another map without the marker on the site. That would require yet another custom template..?

It would be nice to hear some enlightment on the topic. Otherwise 5.6 seems to running fine and has many great features. Thanks core team for the job you've done.

 
Job replied on at Permalink Reply
Job
As per upgrade notes found here (http://www.concrete5.org/documentation/background/version_history/5-6-0-release-notes/) is why the JS was moved ^^.

"Cleaned up javascript in the google map block (thanks Remo)."

Just house keeping.
Ale replied on at Permalink Reply
Yeah I noticed that too, but I'd like to know if the cleaning measure was really that beneficial? I'm fine with that if there are good reasons for it, but in my opinion it just made things unnecessarily complicated.

The question is, why? :)
JohntheFish replied on at Permalink Reply
JohntheFish