Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clustering #20

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

Conversation

damianflannery
Copy link

Hey Cyrill,

I enjoyed your Polaris talk at Droidcon UK last week and thought I'd contribute something.

So I added a Clustering feature for it. The implementation is fairly self contained; I had to make some additions to the Annotation class but don't worry it won't break anything downstream! Everything else is nicely separated out into a 'cluster' subpackage.

I also updated the Polaris sample project so that you can easily toggle the feature on and off.

Take a look and let me know what you think. It would be great if you can use it.

Thanks for creating the project and keep up the great work!

@mooreds
Copy link

mooreds commented Jan 3, 2013

Hi,

Is this any closer to making it into the library? It would be a killer feature!

Thanks.Dan

@intrications
Copy link

@mooreds You can use the feature now by pulling from damianflannery's clustering branch (https://github.com/damianflannery/Polaris/tree/clustering). I'm using it in an app with no problems.

Obviously it'd be better merged into the original library but, if you need it now, you can use it.

@cyrilmottier
Copy link
Owner

Hi,

I'll be honest here. I haven't taken time to work on Polaris lately because of the recent release of the Google Maps Android API v2. The new API contains almost all of the features I developed in Polaris. Moreover when releasing v2, Google also deprecated v1 which basically means they deprecated Polaris :(. As a consequence I don't think it worth working on a new version of Polaris.

As @intrications said, you can still pull @damianflannery's clustering branch. I know this is not perfect but that's an option.

Cyril

@intrications
Copy link

Not only is v1 deprecated, you won't be able to get any new API keys from Google from March 3, 2013, so it really is a dead end:

http://commonsware.com/blog/2012/12/17/maps-v1-keys-going-going.html

@mooreds
Copy link

mooreds commented Jan 4, 2013

Ah, thank you both very much! Might it make sense to push this information to the README.md file so other folks will see that this project is deprecated along with the google maps API v1?

@cyrilmottier
Copy link
Owner

I'll try to do it in March :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants