Live data from Hacker News

KickStarter project: a multi mapping JS client-side clustering library

kickstarter.com

1–7 of 7 posts

Re: KickStarter project: a multi mapping JS client-side clustering library

#3
post #2

Instead of reinventing the wheel, why not make this library work with the wrappers provided by Mapstraction? http://mapstraction.com/ Edit: Sorry, didn't notice the part about leaflet earlier. But yeah, Mapstraction support would be nice.

Maybe the clustering project could be made compatible with Mapstraction rather than fully dependent (if that's what you suggest?).

(note that I'm not the KS project runner, just a thought!)

Re: KickStarter project: a multi mapping JS client-side clustering library

#4
post #2

Instead of reinventing the wheel, why not make this library work with the wrappers provided by Mapstraction? http://mapstraction.com/ Edit: Sorry, didn't notice the part about leaflet earlier. But yeah, Mapstraction support would be nice.

I will provide API for leaflet which is also a wrapper. I'll take a look to Mapstraction and definitively support it to

This goal is to make something very easy to extend.

Re: KickStarter project: a multi mapping JS client-side clustering library

#5
post #2

Instead of reinventing the wheel, why not make this library work with the wrappers provided by Mapstraction? http://mapstraction.com/ Edit: Sorry, didn't notice the part about leaflet earlier. But yeah, Mapstraction support would be nice.

I will provide API for leaflet which is also a wrapper. I'll take a look to Mapstraction and definitively support it to

This goal is to make something very easy to extend.

Re: KickStarter project: a multi mapping JS client-side clustering library

#7
At first, I thought that the guy was using KS as an exit strategy from his current startup, Maptimize. Then I realized that he was creating a new, open-source JS client-side library, which is a real need. Kudos to that!

What strikes me is how one could use KS to "sell" useful code/assets from a failed startup. Or, to an extend, use KS as an exit strategy - going open source instead of going public.