workaround for SSL issues needed

apart from the fact I hear people saying it’s not working with 3.1.2 anyway, one thing I noticed is, I immediately get non-secure warnings (more or less dramatic depending on browser) on SSL pages as soon as I activate the plugin. This is because as soon as it’s activated, it integrates google API.

I think, we need two things to get this improved. First would be an option to use SSL for Google maps API premier customers (although I’m not expecting this league so much in the wp world, if I read that it’s about $10k/y), and the second one would be to load the API on demand only, to have the option to exclude certain pages or posts that contain google maps from SSL and be fine.

Additionally it makes sense to load as few javascript as possible anyway, as this improves loading times.