Sun Feb 08, 2009 // 22:32

Round two of stalker enabling

In retrospect, iframe was a retarded choice. With as much XMLHttp stuff as I did this fall you'd think I'd have turned toward that initially. Well eating dinner managed to kick my brain into gear and I re-factored how I handle the BrightKite map support. Basically the application will serve up an img tag to be used in an iframe, XML, or JSON. Using Dojo I changed the page to make a call to the JSON response type. This required moving the 'display' portion of the app over to the afterfate.net vhost instead of apps.afterfate.net but that isn't too bad. Most of the 'work' for this app is handled by the back-end components which come off the same place in the filesystem.

The worst part is up until about two hours ago 'apps.afterfate.net' hadn't even been registered, so the iframe wouldn't have worked for anyone who wasn't NIS bound here in the _house_.


permanent link

Fun with google maps

I was bored this weekend with the typical fare. I decided I would take a cue from @ffg and 'stalker enable' my blog using the google maps API. On the back-end it's powered by a mason app loaded in an iframe on the blog's main page. Eventually I want to see if I can make a simple facebook app to throw this into the facebook profile side-bar. For now having it on my blog is fine. Before anyone shouts 'but privacy!', I'm not going to check in unless I want just about everyone to know where I am, duh.

I'm not sure if an iframe is the best way to do this, but I don't see any reason for the image to come off of afterfate.net rather than google itself. Since the afterfate.net/ blog is completely static I can't just make a call to my google maps code.


permanent link