In any case, I got this sent to my comcast.net email address this morning:

Dear MATTHEW AUAYAN,

Our records show that you recently changed the email password on your account. If you did not authorize this change, please call Comcast at 1-800-COMCAST and we'll be happy to assist in any way we can.

Your security is top priority at Comcast! To learn more, visit our FAQs at www.comcast.com.

Best regards, The Comcast Team\r\n[EventId:60097249:/EventId]

I bet when my Comcast phone service goes out, they diligently call me on my Comcast phone line to notify me of the interruption of service¹.

I'll try and flesh them out over time.

Seattle JS Community

• meetup.com/seattlejs
• meetups.jquery.com

Upcoming jQuery Mobile Blog

• jquerymobile.com

Current Mobile Browsers

• Opera 9.5,10
• IE6,7
• FireFox 3.5+
• Safari 2,3,4
• Blackberry

A-grade Devices

• iPhone 3gs, 3.x
• iPad, 3.2
• Nokia N97 S60VG
• Palm Pre 1.4
• HTC Magic
• Droid

B-grade Devices

• iPhone 2.x
• Nokia N96
• Curve
• Storm
• HTC HD2

Notes

Use cache manifests, html storage for cacheing libraries on modern browsers. See also: http://github.com/wycats/jquery-offline

Resources

http://quirksmode.org/mobile/ http://github.com/jquery/jquery-tmpl

First, do this:

1. Find Safari.app in your Applications folder
2. Right click
3. Click 'Show Package Contents' from the context menu

Then, find this (you'll probably want to save a copy of this in case you want to revert):

1. In the new Finder window, go to the Resources folder
2. Find Reader.html
3. Edit with whatever editor you're comfortable with.

Then, make some changes and save:

You might be asked for your admin password when you save. I set text-align to left because that's how I roll.

Before:

After:

Seriously though, if you don't know what you're doing… please don't even attempt.

Screenshot

An Early Screenshot (note to self: replace with updated screenshot)

It's all JavaScript, CSS3 and HTML5. The gauges are all built and controlled with a JavaScript library that I developed, and are rendered with CSS3. The only images are the footer bar texture and the logo¹ (I know, looking at that screenshot, it's hard to believe).

I built this for two reasons. The first being that I wanted a rotary gauge JavaScript library (for use in another unrelated project), and the second being that I wanted to demonstrate (mostly to myself) how feasible these WebKit apps really are.

Installation

When you go to the app's URL, you'll be given instructions on how to install it (it's as simple as bookmarking it to your homescreen). Then, when you launch it, it will download and cache all the assets², and each subsequent launch after that will check for updates if your device has network access.

How it works

Basically, the app calculates how fast you're going by getting the distance between your current position and your last position and dividing that by how long it took to get there. There are other things going on, like soft rejecting³ positions that would seem to indicate an acceleration of anything above 2g⁴.

This could be further optimized, of course, and when I do that, I can push those changes and everyone (with a network connection) will have access to the new version as soon as they launch.

Features

• A speedometer
• A bearing indicator (it tells you what direction you're heading)
• An analog clock

The clock was really just an exercise for myself. It's basically a rotary gauge with 3 custom indicators with their own values.

If you have an idea for what should be there instead of the analog clock (or any other feedback, really), feel free to let me know. I'm also on twitter.

Sidenote(s)

Debugging and testing this isn't easy. While iPhone can hit .local domains on a local network, I couldn't exactly do use a local network to test this app. I had to be in motion. I spent time while commuting to do my testing and debugging. I also needed full access to the internet to update the remote servers so the iPhone could access the app. I don't think I could have done this without tethering⁵.

I might have been able to create a WiFi network with my MacBook to get access to the .local domain, but even in that case, I'd have to configure my development environment to serve this app from my .local address, and that's also not ideal. Meh, I'll figure out the best solution eventually.

Forgive my rambling, I had to be up early this morning (like, so early it was still Saturday for another 30 minutes).

Many people, myself included¹, assumed that onmouseover was dead² with the arrival of touch based web browsers, and up until iPhone OS 3.2 that seemed to be the case. However, in my testing, I've found that the first tap on an element with an onmouseover "attribute" will trigger the onmouseover event, stop the click event from propagating to any children until a second tap after the onmouseover has fired.

Setting focus elsewhere (via tapping other onmouseover watching elements or form fields) will trigger the onmouseout event and, again, tapping on the element a second time while the onmouseover is active sends the click down to its child elements. You can see this in action with Twitter's "hovercards".

Sadly, adding those behaviors using jQuery doesn't seem to give it the same magic. Perhaps we'll see it in the next version of MobileSafari, and hopefully on iPhone as well. These are preliminary findings, of course, and in order to do more testing I'll require an iPad (with 3G, please).

Anyone?

It basically does what it says on the tin. Enjoy!

• Pre-Phase Phase (I'm not good with phases)
• Phase 1 - Fuel for your Future
• Phase 2 - Secure your Food
• Phase 3 - Home Compound
• Phase 4 - Self Preservation
• Phase 5 - Recreation
• Phase 6 - Keep your mind busy
• Final Phase - Seal your fate.

/via kottke

Instead of designing beautiful data-structures and elegant algorithms, we’re looking up the EnterpriseFactoryBeanMaker class in the 3,456-page Bumper Tome Of Horrible Stupid Classes (Special Grimoire Edition), because we can’t remember which of the arguments to the createEnterpriseBeanBuilderFactory() method tells it to make the public static pure virtual destructor be a volatile final abstract interface factory decorator.

After work, I played Modern Warfare 2 (on the PS3 — you can probably guess what my PSN name is) and set a personal kill streak record (22 kills!) and played a match without dying.

I reapplied thermal paste on Nicole's MacBook. I don't know why, but from the factory it looks like they applied thermal paste like its purpose was to insulate these chips.

Last December, my nephew accidentally bumped a table, causing a glass of water to spill right into the back vents. I took the MacBook apart completely, hunting for liquid, but I'm guessing a combination of Nicole's quick reaction, winter's insanely dry air, and the insanely hot wood stove at my parents', and just taking it apart took care of it all. Of course, I didn't have any thermal paste at the time and combine that with the incredibly thick layer that was laid down... you can imagine it wasn't doing it's job very efficiently.

I figured out the best thing to use to apply thermal paste is the back of a plastic spoon. While I'm at it, allow me to also give you a couple more, what the french call, le pro-tips:

• Use tape, sticky side up, to keep screws from getting lost. I also keep the screws arranged analogously to their spatial relationship of the machine I'm taking apart. Keeps me from getting lost, as well. A large magnet might work as well, but I've got a semi-irrational fear of large magnets in proximity to computers¹.

• Stick a small magnet on your screw driver to temporarily magnetize it, to keep the tiny little screws from falling off and into your machine. Yeah, I know what I said in the last tip. Please also note that I qualified that with "semi-irrational".

• Backup before you do any of this. In fact, backup before you backup.

Now, I'm blogging it up while eating a bowl of ramen, as if I were some sort of nerd.