Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Adapt API to match polymaps #46

Closed
tmcw opened this Issue · 2 comments

2 participants

@tmcw
Collaborator

There are many API differences from polymaps that could be eliminated - getZoom() and setZoom(x) instead of just zoom() and zoom(x), etc. Personally, I find the polymaps API to be pretty solid and it'd be nice if one could swap out a lot of the functionality of the two toolkits without these more-nitpicky tweaks.

@RandomEtc

If you're writing libraries that can back onto either MM or polymaps it's trivial to write a compatibility layer, so I strongly disagree here.

I like the (admittedly java-esque) set/get routines, and badly miss verbs when in polymaps land. Much love to polymaps: I've learned a lot from it and it's extremely concise and elegant, but the overloaded getter/setters aren't free of overhead (conceptual or otherwise).

@tmcw
Collaborator

All right; this is low-priority. I'll axe for now.

@tmcw tmcw closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.