SomedayMaybe

h3. Someday/Maybe * [[@Create GUI Wiki editor for MoinMoin]] * [[@PopNotes]] * @Make Redcloth robust * @Complete Swing Set * Update 2-minute timer to have an option of just playing a sound, or flashing the screen instead of a dialogue. * Create a realistic backup plan for all home plus laptop disks. * @Whizbang Uber Program * @Reread GTD * Move past 'good enough' * @Insurance Coverage Right-size and Right-cost * Publish new hardskills articles. * Publish new softskills articles. * Dance Dance Revolution * Could I use PSK for proof it is me in email?

* How to lower triglycerides? * How to walk daily? * How to lose weight? * Research Internet for bone loss and tooth loss. * Kleenex to work * Eye doctor appointment * Seyfried appointment * Shop for another 250+GB drive. * Read Up on Google Technology

Read up on Google technology

* Try adding "&output=xml" to any google map url. Gives you the same results (map, local search, directions) in XML format. * More on the GFS here: http://labs.google.com/papers/gfs.html * You CAN de-encode the polyline data. The JS function to do it is in maps.1.js and is called, not surprisingly, Lb.prototype.decodePolyline. I translated it to Perl and ran it for my own test data, then imported the results into Street Atlas 2003 and they matched nearly perfectly (the Google route was actually more true to the streets as they actually exist than the SA route.)

* The magic happens in "gb.prototype.getBitmapCoordinate=function(Ka,Pa,J,e){" in http://www.google.com/mapfiles/maps.1.js ** The gb object contains all the code for transforming lat/lon to bitmap coordinates. ** It's not a hard problem, it's a simple affine transformation. ** They just create a lookup table by zoom level, and then do some subtraction and multiplication. ** Not too comlicated, just hard to piece together from their obfuscated js.