Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

A port of the Android Compatibility package which makes FragmentActivity extend MapActivity. This is a hack to make it possible to use a MapView in a Fragment.

This branch is 0 commits ahead and 0 commits behind master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 samples
Octocat-spinner-32 v13
Octocat-spinner-32 v4
Octocat-spinner-32 v7
Octocat-spinner-32 volley
Octocat-spinner-32 .classpath
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .project
Octocat-spinner-32 NOTICE.txt
Octocat-spinner-32 README.md
Octocat-spinner-32 RELEASE_CHECKLIST.md
Octocat-spinner-32 UPDATE_CHECKLIST.txt
Octocat-spinner-32 build-splitted.xml
Octocat-spinner-32 build.xml
README.md

Android Compatibility Lib + Google Maps Hack

About

A port of the Android Compatibility package which makes FragmentActivity extend MapActivity. This is a hack to make it possible to use a MapView in a Fragment.

- from Massimiliano Leone (second version improved) -

  • fixed bug in FragmentManager, using patch from ActionBarSherlok details
  • added MapFragment (inspired by Pete Doyle sample, with some improvements)
  • providing also "build-splitted.xml": it allows to compile distinct jars, "core" and "maps":
    "core" is original compatibility library with petedoyle,9re and my modification needed in order to have eventually maps support;
    "maps" includes classes for maps support: FragmentMapActivity, MapFragment, and so on.

    This split can be useful if you want have a compliant maps support library but you don't want add maps support to your project, because you don't still need it (but in a future version, you should do)

- from Taro Kobayashi fork (second version) -

Not as Doyle version, where FragmentActivity inherits from MapActivity, here we have FragmentMapActivity inheriting from MapActivity.
More interesting details here:
http://uwvm.blogspot.it/

- from PETE DOYLE's Readme (first version) -

Downloading

For pre-compiled .jar files, visit the Downloads page.

Building

You can build the jar using Ant:

git clone git://github.com/petedoyle/android-support-v4-googlemaps.git
cd android-support-v4-googlemaps
ant

The default Ant target will build the jar and place it in the build/jar folder.

Alternatively, the source also includes an Eclipse project which you can use to add it as a build dependency for your project. Import it into Eclipse using File > Import > Existing Projects into Workspace..., then configure the build path of your project to require the android-support-v4-googlemaps project.

Changelog

March 28, 2012

New release based on r7 of the Android Compatibility Library.

December 16, 2011

Released android-support-v4-r6-googlemaps.jar and android-support-v13-r6-googlemaps.jar based on revision 6 of the Android Compatibility Library. This also includes a fix for Android bug #22226.

This also includes the additions from Google's r5 release. For the changelog of what changed in ACL r5 and r6, see http://developer.android.com/sdk/compatibility-library.html.

October 27, 2011

Released android-support-v4-r4-googlemaps.jar and android-support-v13-r4-googlemaps.jar based on revision 4 of the Android Compatibility Library. This release, like the official release from Google, splits the ACL into two jars (v4 and v13). The v13 jar contains all the v4 classes plus the classes in the android.support.v13 package.

For the changelog of what changed in ACL r4, see http://developer.android.com/sdk/compatibility-library.html.

July 22, 2011

Released android-support-v4-r3-googlemaps.jar based on revision 3 of the Android Compatibility Library (see downloads). FragmentPagerAdapter and FragmentStatePagerAdapter are also included from the new android.support.v13 package.

May 24, 2011

Released android-support-v4-r2-googlemaps.jar based on revision 2 of the Android Compatibility Library (see downloads).

Limitations

Currently, one downside is that ALL classes extending FragmentActivity are MapActivitys. Its possible to make a separate class (i.e. FragmentMapActivity), but it requires some refactoring of the FragmentActivity code. Feel free to file a bug to request it or fork this project to fix it.

Getting Help

Need help? Check out this project's Google Group.

- end Pete Doyle readme -

Something went wrong with that request. Please try again.