So, it looks like the only phone thus far that can use these calculators is… the iPhone. Don’t blame me – blame every other cell phone maker out there. I played with an LG Dare again a few days ago and was disappointed with its web browser this time.

I’m sure its a great phone. But, let’s be real, that’s not good enough any more.

Pros:

  • Touch screen
  • Virtual QWERTY keyboard
  • A screen that rotates when you tilt the camera
  • MP3 player
  • Digital camera, video camera
  • Removable memory chip
  • 500 contact with up to 5 phone numbers each
  • A web browser that will support AJAX and XMLHttpRequest
  • Decent support of cascading stylesheets

Cons:

  • Imperfect support of javascript
  • No support of cookies/sessions

What does this mean for you? You can go to my site, but you can’t log in. If you can’t log in, you can’t use the calculators. :/

As a side note, just about every Verizon rep I’ve talked to pushes this phone’s 500 person contact list. My question, “How much memory does the phone have?” Their response: “It has 5 phone numbers per contact? Wow. That’s a lot. I didn’t know that.” Riiight – you didn’t know? Why have I heard that exact line from three separate reps? I don’t have 500 contacts. I don’t even know 500 people.

Verdict: It may be a good phone, but you won’t be able to use my calculators from it.

I recently gave a brief overview of my permanent disability and workers’ compensation benefit calculators. In that post I wrote a little bit about how my website calculators work.

In late 2004 I spent some of my free time working on a calculator for the 1997 Permanent Disability Rating Schedule 100% pure javascript (the only programming language I knew at the time). I had several reasons for never publicly releasing this calculator:

  • Uniformity. Not all computers and browsers perform all javascript functions the same way.
  • Speed. A pure javascript calculator would require the user to download all of the code – not just the parts they needed.
  • Protection. Anyone with a modicum of technical knowledge could simply downloaded the calculators, and then post it as their own.
  • Obsolete. With SB 899 and the 2005 Permanent Disability Rating Schedule, my calculator became nearly obsolete. I scrapped it rather than building a second calculator.

The current workers’ compensation benefits calculators use very very little javascript. Doing so has meant that I don’t have to worry about different computers/browsers, users only need to download the code they need to run a single calculation, and my calculators don’t work without my server.

Next up, PHP!