Quoted

The Maps API for Flash was officially deprecated on September 2, 2011 but will continue to be supported for existing applications in accordance with the deprecation policy defined in the Maps API Terms of Service Consequently we recommend against using the Maps API for Flash in any new applications, and instead recommend use of the JavaScript Maps API v3.

Although we are no longer issuing keys for the Maps API for Flash online, we understand that some existing developers may need to update the key being used for an existing application, for example due to a change of hostname. Please mail flash-maps-key-request@google.com if you need a new key. Please provide:

a) a link to your application
b) your reason for needing a new key
c) the hostname for which you need the new key to be issued
d) your existing Maps API key for this application

Please include as much detail as possible about your particular case.

Note that in accordance with the Terms of Service your application must be publicly available to all users at no charge. If your application is not available publicly, or is sold for a fee, you will need to purchase a Maps API for Business license. This will also allow you to self manage the hosts authorised to use your credentials going forward.

Quoted

do you plan a Google map JavaScript version in a short time?

Quoted

Is there something planned for the plugin?

• This plugin would need to be split into two parts: a Flash part that handles the plugin position and size and the krpano xml interface, and a Javascript part that shows and controls the HTML window of the Javascript Google Maps. That means these parts are constantly communicating together about all changes.
• Advantages:
  
  • it would be possible to use Google Maps again
• Disadvantages:
  
  • it would be necessary to use 'wmode=opaque' when embedding the Flash to allow overlapping the Google Maps HTML window the krpano Flash window - this means slower rendering and no 3D GPU usage (the Flash Stage3D GPU rendering will be only possible with 'wmode=direct' and then overlapping HTML content is not possible!)
  • no Flashplayer fullscreen mode - in Fullscreen mode only Flash elements will be visible and so the HTML Google Maps window will be not visible (the new HTML5 Fullscreen mode might be an alternative here, but it is not provided by all browsers yet)
  • no overlapping of krpano xml elements and the Google Maps! That means no "parent" mixing or placing custom buttons/elements on the map.
  • still depend on Google, no idea what will happen on the next API changes...
  • still a bit unclear situation about the new Google Maps limitations and costs for excessive usage.

• I'm still exploring that option...
• Advantages:
  
  • probably the solution that can be implemented in the shortest time.
• Disadvantages:
  
  • still no Google Maps.
  • depend again on a third party Maps API provider.
    

• Instead of using an API from an third party to display the map tiles, it would be also possible to do that by own code. The loading of the map tiles will be only one very small part of the code and can be changed/adopted quickly.
• The problem - I'm not sure which map providers are legally allowing direct tile access, e.g. Google definitely not, but it seems Bing and OpenStreetMap are allowing that.
• Advantages:
  
  • independence from any third party API providers.
  • big parts of the maps code will be usable for the Flash and HTML5 version - this means faster development and better cross Flash-HTML5 support.
• Disadvantages:
  
  • unclear situation about legal tile access:
    
    • Google Maps - technically possible but definitely not allowed.
    • Bing Maps - a bit unclear, eventually allowed, if possible this seems to be the best solution.
    • Yahoo Maps - ?
    • OpenStreetMaps - seems yes, but it has unfortunately no satellite images.
    • other Maps providers - ???
      

Quoted

The Flash Player should still be supported of course, for compatibility with older browsers and with IE. But looking at the way the web is going, it seems to me that features should come first to the HTML5 viewers (WebGL + CSS 3D Transforms), and added to Flash only if it's not too much work. For instance, Google Maps could be available in the HTML5 viewers but not in Flash.

Quoted

Option 2 - Use a different Maps API from an other provider

• I'm still exploring that option...
• Advantages:
  
  • probably the solution that can be implemented in the shortest time.