I admit, this is my first time looking deeper into Maps API. There’s been a lot of overhaul since my last visit a long time ago. There’s this mapplet thing, promising to be able to make maps based app in within 5 minutes. I totally hooked on it.

I have these several data in my kitchen sink. I’ve created several Dapps and pipes. I thought why not using them for some fun activities with Maps API. There’s this geocoder object capable of translating human-readable address into machine-understandable number. OTOH, I have a city list from 21cineplex.com available via Dapper/Pipes. Voila, with a little _IG_FetchContent method and a few lines of javascript (in fact, it’s available on geocoder example) I can make a marker for every city having 21cineplex theater. And to go further, I’ve also made a dapper capable of fetching now playing list from a certain city_id. Okay, this would be great. I’ll fill the marker with now playing list, on demand when user clicked the marker. And the marker for the cities will be initialized with realtime data as well. Now, that’s what I call mashup. A pure mix and match on the web. I don’t even need to provide any backend or space nor bandwidth for hosting purposes.

Too good to be true. If only Dapper is not having error when fetching from 21cineplex.com site, I’d have been able to show something cool now. There’re two possibilities: the error is exclusively on dapper side, or 21cineplex.com is blocking dapper user agent from fetching their content. And if the later is what really happen, then it would be a total-foolness-moron-score-one-they-do-not-get-web-two-point-oh curse.

Powered by ScribeFire.

Sphere: Related Content