Oops! This is one of those things that was supposed to be rewritten but never did. I guess the lesson is to be more careful about leaving snarky comments in public-facing copy... you might forget to change it.
Thanks for the reminder, this will be fixed this afternoon :)
Nice. However, too bad that on scrolling you set a "position:fixed;" style on the map/calender part. On my netbook screen, I can only see the first row of days on the calender, and because of position:fixed, I can't scroll down to see the rest.
I'm on a MacBookPro. I cannot scroll anymore. The [Add Event] button is obscured. The calendar is doing weird things with the menu - why doesn't voost go over it like the rest?
The problem with wheel-to-zoom is that it breaks the mac touchpad experience (and presumably other trackpads that support gestures). When you use two-finger scrolling, you move the page down until the mouse cursor happens to run over a map section, then the page stops scrolling and you start zooming. It's really annoying.
We explicitly turn off wheel-to-zoom. I suspect most sites do it for the same reason.
Most of our "real" users will probably pick a reasonable boundary around their home and leave it there for their lifetime, so disabling the wheel is probably the right decision for us. If our users did a lot of zoom navigation, we'd probably go the other way.
Unfortunately mobile devices handle the transition of the map element from position:static to position:fixed poorly. It's something we still have to figure out. Thanks for the heads up though!
Yes, using the free MaxMind database. We would rather use the geo data appengine provides but our SSL is proxied by CloudFlare and GAE doesn't recognize the forwarding headers yet.
https://www.voo.st/