1、 中文 4128 字 毕业设计 (论文 )外文资料翻译 外文出处 Mark Murphy.Beginning Android 2 Chapter 33 1 Mapping with MapView and MapActivity One of Googles most popular services-after search of course-is Google Maps, which lets you find everything from the nearest pizza parlor to directions from New York City to San Francisc
2、o (only 2,905 miles!), along with supplying street views and satellite imagery. Most Android devices, not surprisingly, integrate Google Maps. For those that do, there is a mapping activity available to users directly from the main Android launcher. More relevant to you, as a developer, are MapView
3、and MapActivity, which allow you to integrate maps into your own applications. Not only can you display maps, control the zoom level, and allow people to pan around, but you can tie in Androids location-based services (covered in Chapter 32) to show where the device is and where it is going. Fortuna
4、tely, integrating basic mapping features into your Android project is fairly easy. And there is also a fair bit of power available to you, if you want to get fancy. Terms, Not of Endearment Integrating Google Maps into your own application requires agreeing to a fairly lengthy set of legal terms. Th
5、ese terms include clauses that you may find unpalatable. If you are considering Google Maps, please review these terms closely to determine if your intended use will not run afoul of any clauses. You are strongly recommended to seek professional legal counsel if there are any potential areas of conf
6、lict. Also, keep your eyes peeled for other mapping options, based on other sources of map data, such as OpenStreetMap (http:/www.openstreetmap.org/). Piling On As of Android l.5, Google Maps is not strictly part of the Android SDK. Instead, it is part of the Google APIs add-on, an extension of the
7、stock SDK. The Android add-on system provides hooks for other subsystems that may be part of some devices but not others. NOTE: Google Maps is not part of the Android open source project, and undoubtedly there will be some devices that lack Google Maps due to licensing issues. For example, at the ti
8、me of this writing, the Archos 5 Android tablet does 2 not have Google Maps. By and large, the fact that Google Maps is in an add-on does not affect your day-to-day development. However, bear in mind the following: You will need to create your project with a suitable target to ensure the Google Maps
9、 APIs will be available. To test your Google Maps integration, you will also need an AVD that supports the Google Maps API. The Bare Bones Far and away the simplest way to get a map into your application is to create your own subclass of MapActivity. Like ListActivity, which wraps up some of the sma
10、rts behind having an activity dominated by a ListView, MapActivity handles some of the nuances of setting up an activity dominated by a MapView. In your layout for the MapActivity subclass, you need to add an element named, at the time of this writing, com.google.android.maps.MapView. This is the lo
11、nghand way to spell out the names of widget classes, by including the full package name along with the class name. This is necessary because MapView is not in the com.google.android.widget namespace. You can give the MapView widget whatever android:id attribute value you want, plus handle all the la
12、yout details to have it render properly alongside your other widgets. However, you do need to have these two items: android:apiKey, which in production will need to be a Google Maps API key android:clickable=true, if you want users to be able to click and pan through your map For example, from the Maps/NooYawk sample application, here is the main layout: com.google.android.maps.MapView android:id=+id/map android:layout_width= fill_parent android:layout_height=fill_parent android:apiKey= android:clickable=true /
