In terms of development, what capabilities does Google Earth Plugin have over Google Earth?
|
Google Earth can display a number of file formats, which may be generated programmatically, but in general the user controls the interaction. The Google Earth Plugin can use the rich set of tools available for web development, and allows DOM manipulation of the data used within the earth environment. You can interact with the user environment, modifying the layers and how they are displayed. |
|||
|
|
|
I think with enough tweaking you can achieve almost anything that one can do in the other, but you might be pushing limits of edge cases. In more general terms, I think one difference is that the Google Earth Plugin can be programmed, and Google Earth is a viewer. In more detail, Google Earth is a viewer of KML/KMZ files and data layers. Because layers can auto-update (based on time, viewport, location, etc.) you can achieve some advanced features. Because you can record and then play back, you can also make "movies" in Google Earth. On the other hand, the Google Earth Plugin can be much more interactive, or even active without the user input. It is easier to push data using asynch client/server techniques, manipulate the DOM, etc. |
|||
|
|
|
I'm not sure what 'In terms of development' means here, do you mean 'for developers'? I'm assuming you don't and that you just want to know what capabilities the GE Plugin has over the GE client. Adding to what has been mentioned already:
None of these features are available in the plugin but you can view tours/network links and all other KML features and use other GE features like navigating. However, the plugin has features that the client does not have:
|
|||
|
|
