<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>tjameswhite</title>
	<atom:link href="http://tjameswhite.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://tjameswhite.com</link>
	<description>My infrequent thoughts, ideas and ramblings.</description>
	<lastBuildDate>Thu, 01 Jul 2010 03:09:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Rethinking a Table with Media Queries</title>
		<link>http://tjameswhite.com/archives/rethinking-a-table-with-media-queries/</link>
		<comments>http://tjameswhite.com/archives/rethinking-a-table-with-media-queries/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 02:58:54 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[(x)HTML]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[@media]]></category>
		<category><![CDATA[media queries]]></category>
		<category><![CDATA[table data]]></category>

		<guid isPermaLink="false">http://tjameswhite.com/?p=535</guid>
		<description><![CDATA[Attending An Event Apart Boston and going through the W3C&#8217;s Mobile Web Best Practices course has me looking more closely at how I mark up data. 
The main cord that was struck, most directly in Luke Wroblewski&#8217;s Mobile First! talk, but echoed by most every speaker in Boston, is to design from the mobile version [...]]]></description>
			<content:encoded><![CDATA[<p>Attending <a href="http://aneventapart.com/2010/boston/" rel="external">An Event Apart Boston</a> and going through the <acronym title="World Wide Web Consortium">W3C</acronym>&#8217;s <a href="http://www.w3.org/2010/03/MobiWeb107/" rel="external">Mobile Web Best Practices</a> course has me looking more closely at how I mark up data. </p>
<p>The main cord that was struck, most directly in Luke Wroblewski&#8217;s Mobile First! talk, but echoed by most every speaker in Boston, is to design from the mobile version of your site <strong>first</strong>.  This theme occurs in the Mobile Web course as well.<br />
<span id="more-535"></span><br />
For exercises in the Mobile Web course we have to consider mark up that is mobile friendly. Consider, if you will, a simple data table. In a desktop browser, a table is easy enough to render. See, a <a href="/demos/media-queries/simple-table.html">simple data table</a>. </p>
<p>However, on a mobile device with its much narrower screen, a table simply won&#8217;t fit. Instead, the data may be better presented in an alternate form, such as a definition list. (Please note, this is but one example and does not mean that all tables can be equated to a definition list.)</p>
<p>Call me Marie, but I want to have my cake and eat it to.</p>
<h3>Enter the Media Query</h3>
<p>So what is a media query? There are <a href="http://www.google.com/search?hl=en&amp;q=css%20media%20query&amp;aq=f&amp;oq=" rel="external">lots of resources out there</a>. Let me sum it up: media queries allow you to specify CSS rules base not on a device, but on a set of circumstances.</p>
<p>The following block of code applies to any device that claims to be a screen. It will simply make level 1 headers blue:</p>
<pre><code>@media screen {
  h1 {color: blue;}
}</code></pre>
<p>Let&#8217;s through a query into the mix:</p>
<pre><code>@media screen <ins>and (max-width: 500px)</ins>  {
  h1 {color: red;}
}</code></pre>
<p>Now the style applies to any device that claims to be a screen <strong>and</strong> has a width of 500px or less. There are several other properties that can be queried, but this works for our demo.</p>
<p>Let&#8217;s put a query into play on this <a href="/demos/media-queries/floating-query.html">simple demo page</a>. You should see a green masthead across the top of the page and two gray boxes sitting next to each other. Now narrow your browser.</p>
<p>When your browser gets to 500px wide you should see the green masthead change to gray and the gray boxes become blue and stack on top of each other. The code is quite simple:</p>
<pre><code>@media all and (max-width: 500px)  {
	#header {background: #ddd;} /* little color change */
	.column {
		float: none; /* linearize */
		width: 95%; /* reset width */
		background: #6374AB;
		color: #FFF;
		}
}</code></pre>
<h3>The Trouble with Tables</h3>
<p>Let&#8217;s take the same page and <a href="/demos/media-queries/data-table.html">add our simple table to it</a>. Looks fine so far, right? Now narrow your browser.</p>
<p>Once again at the threshold of 500px you should see the boxes stack and the colors change. But this time there is a horizontal scroll because the table needs to be wide enough for it&#8217;s content.</p>
<p>The problem: we came at this from the desktop first. What if we reversed that and thought about the small screen first, then adapted it for the desktop?</p>
<h3 lang="fr">Ce n&#8217;est pas une table</h3>
<p>For our little demo, it isn&#8217;t too difficult to re-imaging that <a href="/demos/media-queries/definition-list.html">tabular data as a definition list</a> (or series of list in this case), which should work nicely on most any mobile device. The code looks something like this:</p>
<pre><code>&lt;dl&gt;
	&lt;dt&gt;Ekstr&ouml;m&lt;/dt&gt;
	&lt;dd&gt;&lt;span class="label"&gt;Points: &lt;/span&gt;44&lt;/dd&gt;
	&lt;dd&gt;&lt;span class="race"&gt;Race 1: &lt;/span&gt;10&lt;/dd&gt;
	&lt;dd&gt;&lt;span class="race"&gt;Race 2: &lt;/span&gt;2&lt;/dd&gt;
	&lt;dd&gt;&lt;span class="race"&gt;Race 3: &lt;/span&gt;-&lt;/dd&gt;
&lt;/dl&gt;</code></pre>
<p>So we&#8217;ve got our cake. Now to eat it too.</p>
<p>Definition lists are just fine in a desktop browser, but I really want this to be more table-like.</p>
<p>You&#8217;ll notice that there are already some <code>class</code> attributes. We just need to add a little more markup to create what will become the table headers:</p>
<pre><code>&lt;div class="head"&gt;
  &lt;div class="row"&gt;
	&lt;div class="dataHead"&gt;&lt;abbr title="position"&gt;Pos.&lt;/abbr&gt;&lt;/div&gt;
	&lt;div class="dataHead"&gt;Driver&lt;/div&gt;
	&lt;div class="dataHead"&gt;&lt;abbr title="points"&gt;Pt.&lt;/abbr&gt;&lt;/div&gt;
	&lt;div class="dataHead"&gt;Hockenheim&lt;/div&gt;
	&lt;div class="dataHead"&gt;Oscherslebe&lt;/div&gt;
	&lt;div class="dataHead"&gt;EuroSpeedway&lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;</code></pre>
<p>and style with <code>display: table</code> and related properties. For example:</p>
<pre><code>dl, .row {display: table-row;}
.dataHead, dd, dt {display: table-cell;}</code></pre>
<p>(<a href="/demos/media-queries/data-list.css">View the complete CSS</a>)</p>
<p>We now have markup that is mobile friendly styled in a desktop friendly way. All that is left is to undo those desktop styles for small screen display using our media query. Mostly this involves <code>display: block</code> to counteract the table display properties.</p>
<p>The end result: a <a href="/demos/media-queries/data-list.html">desktop and mobile friendly web page</a>. Once again, with a device wider than 500px you should see green color and a basic table. Narrow your browser to less than 500px &hellip; presto! our definition list re-emerges.</p>
<p>I&#8217;ve used a similar media query on this site. Narrow your browser and it should revert to one column.</p>
<h3>Caveat</h3>
<p>No, this is not a perfect solution. It is <em>a</em> solution. If you look at the full code you will see some markup that may be questionable (the first <code>dd</code> in the lists). I merely present this to get us all thinking about they way we think about and markup data.</p>
<p>Your mileage may vary; use at your own risk; objects in mirror may be close than they appear; etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/rethinking-a-table-with-media-queries/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fisheye Effect via CSS</title>
		<link>http://tjameswhite.com/archives/fisheye-effect-via-css/</link>
		<comments>http://tjameswhite.com/archives/fisheye-effect-via-css/#comments</comments>
		<pubDate>Wed, 16 Jun 2010 01:38:42 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[transform]]></category>

		<guid isPermaLink="false">http://tjameswhite.com/?p=527</guid>
		<description><![CDATA[In which we transform.]]></description>
			<content:encoded><![CDATA[<p>On the CSS-d mailing list Gabriele posted a demo titled <a href="http://onwebdev.blogspot.com/2010/06/pure-css-fisheye-menu-with-icons.html">Pure CSS fisheye menu with icons</a>. It&#8217;s a nifty little demo replicating the zooming dock feature you&#8217;ll find on Mac and Stardock&#8217;s Dock.</p>
<p>I decided to take it one step beyond and utilize CSS 3&#8217;s transform properties, resulting in my own <a href="demos/fisheye/">Fisheye demo</a>.</p>
<p>I cut out much of Gabriele&#8217;s code that handled the zooming and replaced it with <del>Folgers Crystals</del> <code>transition</code> and <code>transform</code>. (Although I kept pretty much everything else she built, including her icons. Thank you Gabriele for the inspiration.)</p>
<p>Specifically, on the navigation anchors we have <code>transition: all .1s ease-in-out</code>. In a nutshell, this says, &#8220;All transitions should take .1 seconds to complete and they should do it smoothly.&#8221; We also have <code>transform-origin: 50% 0</code> which moves the center of action to the center top of the anchor box.</p>
<p>It isn&#8217;t until we get to the <code>hover/active/focus</code> states that things happen. Here we have <code>transform: scale(1.5)</code>, which you&#8217;ve no doubt already concluded causes the element to grow by a factor of 1.5. An important thing to note about this, the <code>transform</code> is applied to the anchor element and therefore affect everything <em>inside</em> that anchor, be it a background image, text or foreground image.</p>
<p>Of course it isn&#8217;t <em>quite</em> that simple. Because this part of CSS 3 is under development, we need to utilize various vender prefixes. So to see it actually work you&#8217;ll need to add <code>-moz-</code>, <code>-webkit-</code> and <code>-o-</code> to the front of all the transform properties. Not surprising there is not support for Internet Explorer, but that&#8217;s OK, it doesn&#8217;t matter. Anyone using IE won&#8217;t know what they are missing. Go see for yourself.</p>
<p>And look for the Easter Egg&hellip; .</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/fisheye-effect-via-css/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hell May Be Frozen</title>
		<link>http://tjameswhite.com/archives/hell-may-be-frozen/</link>
		<comments>http://tjameswhite.com/archives/hell-may-be-frozen/#comments</comments>
		<pubDate>Thu, 10 Jun 2010 17:09:24 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[hell freezing]]></category>

		<guid isPermaLink="false">http://tjameswhite.com/?p=525</guid>
		<description><![CDATA[In which the blog lives on.]]></description>
			<content:encoded><![CDATA[<p>Wow, a new post. OK, it&#8217;s mostly to announce that I have moved my blog from there to here (no longer a page of my site, but front-and-center).</p>
<p>I&#8217;ve also cleaned up some things behind the scenes (not that you care, but hey, I did it). There is more cleaning to do, but it shouldn&#8217;t affect you in a negative way.</p>
<p>So, that&#8217;s it for now. Welcome to my new(ish) home. As always, I&#8217;m hoping to use it more&#8230;. Time will tell.</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/hell-may-be-frozen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chrysler 300 Review</title>
		<link>http://tjameswhite.com/archives/chrysler-300-review/</link>
		<comments>http://tjameswhite.com/archives/chrysler-300-review/#comments</comments>
		<pubDate>Thu, 16 Jul 2009 16:47:40 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Automotive]]></category>
		<category><![CDATA[car review]]></category>
		<category><![CDATA[chrysler]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/?p=522</guid>
		<description><![CDATA[While in California a couple of weeks ago, we had a Chrylser 300 rental to get around in. Driving the car for a week did not put Chrysler into my list of potential car purchases.
First Glance
From the outside the car looks OK. Its tall waistline/short windows give it a muscular, aggressive line seen throughout most [...]]]></description>
			<content:encoded><![CDATA[<p>While in California a couple of weeks ago, we had a Chrylser 300 rental to get around in. Driving the car for a week did not put Chrysler into my list of potential car purchases.</p>
<h3>First Glance</h3>
<p>From the outside the <a href="http://en.wikipedia.org/wiki/File:Chrysler_300_.jpg" rel="photo">car looks OK</a>. Its tall waistline/short windows give it a muscular, aggressive line seen throughout most of Chrysler&#8217;s lineup. The 300 is not the most attractive car, but it certainly isn&#8217;t an <a href="http://en.wikipedia.org/wiki/File:2002-05_Pontiac_Aztek.jpg" rel="photo">Aztek</a>. If I was to put it to a 5 star rating, the 300 rolls in around a 3 &frac12; on purely exterior aesthetics.</p>
<p>The interior fairs about the same. The seats were comfortable and the dash was laid out fine. Given my height (6&#8242; and a bit) and seating / steering position, part of the gauge cluster was hard to read. On the plus side, the fit and finish was nice and, with 32,000 miles on the car, it was free of squeaks and rattles. It wasn&#8217;t full-size car plush and fancy, just nice.</p>
<p>One word of caution about the seats: do not drop anything between the seats and the center console.  The seat bracket mount is in an uncovered hole that, despite conventional physics, is far deeper than the floor pan should allow. I had the misfortune of dropping a small Barbie accessory (hey, I was traveling with my 4 year old) into the 3&#8243; deep void. Happily I managed to retrieve the princess crown.</p>
<h3>Driving Impressions</h3>
<p>Ride was big-car cushy. A little bit more wallow than I car for, but very similar to Cadillacs and Lexuses that I have ridden in. Riding in the back seat was less comfortable. While there was enough room for me (on a 2 hour jaunt to Anaheim), the ride was much more jouncy than up front.</p>
<p>From the driver&#8217;s seat, however, the 300 has more blind spots that a <a href="http://en.wikipedia.org/wiki/Macular_degeneration" rel="tag">macular degeneration</a> conference. The short windows combined with overly thick pillars made changing lanes a crap shoot at best. After a couple of days of double-checking mirrors and craning my head around looking for traffic, I simply started to throw on a blinker, count to three and moved lanes. Sorry to those of you in San Diego that I cut off.</p>
<p>Getting around tight spots and parking was also a challenge. The short trunk is completely invisible from inside the car, and the hood only barely visible. After a couple of days I did begin to develop a feel for where the ends of the car were, but I was never supremely comfortable. (Nor, I should say, did I actually hit anything. Always good.) Rating: 2 &frac12; out of 5.</p>
<h4>Drive Line</h4>
<p>Here the 300 really fails to impress. The 6-cylinder engine sort of maybe felt powerful, but that didn&#8217;t actually translate into being powerful. Mashing the accelerator made noise and you wanted to believe that you were muscling away, but the not-vanishing landscape outside the windows told a different story.</p>
<p>But the real problem was the transmission. While cruising The 5 and The 15 (as they seem to say in <a href="http://maps.google.com/maps?f=q&amp;source=s_q&amp;hl=en&amp;geocode=&amp;q=san+diego&amp;sll=37.0625,-95.677068&amp;sspn=40.409448,73.388672&amp;ie=UTF8&amp;ll=32.719132,-117.126617&amp;spn=0.084055,0.143337&amp;z=13" rel="map">San Diego</a>) the 300&#8217;s transmission couldn&#8217;t decide which gear to use &#8212; it was forever hunting between 3rd and overdrive. The slightest elevation change caused it to drop out of <abbr title="overdrive">OD</abbr>. It would then decide no, it didn&#8217;t really need to and shift back up. Upon further reflection, maybe 3rd gear was better after all. And down again it would go.</p>
<p>If there is one continual knock on American cars (and by that I mean The Big Three) is quality. The transmission on the 300 we rented had a rather worrisome &#8220;ka-slump&#8221; that we could feel and hear when it changed from 1st to 2nd gear. And it got worse as the week wore on.</p>
<p>Yes, this was a rental car so we can expect some abuse. I&#8217;ll cut Chrysler some slack and I&#8217;ll call the 32,000 actual miles equivalent to 64,000 miles. And yet my Mazda has 147,000 miles of abusive driving and the transmission is still pretty slick. Likewise my wife&#8217;s 2005 Accord (American-made) with 50,000 miles has zero hiccups. (Full disclosure: her Accord does have a nagging tail light problem and a continually out dome light.)</p>
<p>Drive line rating: 1 out of 5.</p>
<h3>Overall</h3>
<p>The Chrysler 300 failed to impress any of the three people who drove it. Two of us (mother-in-law and myself) are in the market for a new car, and a week with the 300 did not put Chrysler to the top of either list.</p>
<p>Overall rating: 2 out of 5.</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/chrysler-300-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Children&#8217;s Toy Safety Checklist</title>
		<link>http://tjameswhite.com/archives/childrens-toy-safety-checklist/</link>
		<comments>http://tjameswhite.com/archives/childrens-toy-safety-checklist/#comments</comments>
		<pubDate>Mon, 08 Jun 2009 18:16:28 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Life and Things]]></category>
		<category><![CDATA[engrish]]></category>
		<category><![CDATA[safety]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/?p=518</guid>
		<description><![CDATA[In which Engrish strikes.]]></description>
			<content:encoded><![CDATA[<p>My daughter received a Banzai&trade; Wigglin&#8217; Waterpillar&trade; for her birthday. I faithfully present to you the &#8220;Safety Checklist&#8221;:</p>
<blockquote><p>
Setup:</p>
<ol>
<li>Before set up: Check under and around Wigglin&#8217; Waterpillar&trade; for sharp objects, rocks, sticks, lawn sprinklers or any other object that can cause injury or damage to the product. Set up on flat lawn surface, free of depressions or high spots.</li>
<li>The product should be at least 10 feet (305 cm) away on all slides from trees, walls holes, garden equipment, pools and other objects.</li>
<li>Connect a standard water hose (not included) to the attachment on the base of base.</li>
</ol>
<p>[...]</p>
<p>After Use:</p>
<ol>
<li>Turn off water hose when product is not in use.</li>
<li>Detach garden hose.</li>
<li>Do not store Wigglin&#8217; Waterpillar&trade; until all parts are completely dry, away from children, to prevent suffocation.</li>
</ol>
</blockquote>
<p>This is exactly how the instructions appeared. Any and all typos have been faithfully reproduced. I have only left out the &#8220;Use&#8221; section as it wasn&#8217;t very funny.</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/childrens-toy-safety-checklist/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Strange Police Blotter Item</title>
		<link>http://tjameswhite.com/archives/in-which-a-tree-is-stolen/</link>
		<comments>http://tjameswhite.com/archives/in-which-a-tree-is-stolen/#comments</comments>
		<pubDate>Fri, 13 Mar 2009 21:01:49 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Life and Things]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/archives/2009/03/in-which-a-tree-is-stolen/</guid>
		<description><![CDATA[From today&#8217;s Rochester Post comes one of the strangest crime watch notices:

According to a police report, a tree was stolen from the backyard of a home &#8230;.
The tree may have been chopped down and taken away, the report states.

May have been chopped down? They aren&#8217;t sure? Who chops down a tree to steal it?
]]></description>
			<content:encoded><![CDATA[<p>From today&#8217;s <cite>Rochester Post</cite> comes one of the strangest crime watch notices:</p>
<blockquote><p>
According to a police report, a tree was stolen from the backyard of a home &hellip;.<br />
The tree may have been chopped down and taken away, the report states.
</p></blockquote>
<p><em>May</em> have been chopped down? They aren&#8217;t sure? Who chops down a tree to steal it?</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/in-which-a-tree-is-stolen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MRI</title>
		<link>http://tjameswhite.com/archives/mri/</link>
		<comments>http://tjameswhite.com/archives/mri/#comments</comments>
		<pubDate>Sat, 28 Feb 2009 01:55:34 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Life and Things]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/archives/2009/02/mri/</guid>
		<description><![CDATA[Today I had my first MRI and, frankly, that is one ridiculous device. If you are unfamiliar with an MRI, in a nutshell, it is a big noisy magnet that creates several slice images of the body part in question.

That question for me is my shoulder. Specifically we are looking for a glenoid labrum tear.
Because [...]]]></description>
			<content:encoded><![CDATA[<p>Today I had my first <abbr title="Magnetic resonance imaging">MRI</abbr> and, frankly, that is one ridiculous device. If you are unfamiliar with an MRI, in a nutshell, it is a <a href="http://healthguide.howstuffworks.com/mri-dictionary.htm">big noisy magnet</a> that creates several slice images of the body part in question.<br />
<span id="more-516"></span><br />
That question for me is my shoulder. Specifically we are looking for a <a href="http://en.wikipedia.org/wiki/Glenoid_labrum">glenoid labrum</a> tear.</p>
<p>Because we are looking for the cartilage, my first stop was for an injection of contrast dye (<a href="http://en.wikipedia.org/wiki/Gadolinium">gadolinium</a>). A fairly simple procedure, we started with a couple of x-rays to get an overview of my shoulder, then a <a href="http://en.wikipedia.org/wiki/Flouroscope">flouroscope</a> to help the physician insert a needle into the joint into which he then injected the dye.</p>
<p>Probably the most interesting parts of the day were feeling the fluid balloon, at least what felt like ballooning, out the back of my shoulder; and then seeing the remaining image on the fluoroscope screen  of the needle in the midst of my shoulder with the dye coming out. Very interesting that. The downside is that as the Lidocaine wears off and the fluid begins to be absorbed, my shoulder aches.</p>
<p>Next up: the MRI. I have been told the machines can be a bit claustrophobic and noisy. That is an understatement.</p>
<p>I&#8217;m not terribly claustrophobic, so the small confined space wasn&#8217;t a bother. Frankly the inside of the machine reminded me of standing up in an airplane with my face inches from the bottom of the overhead bin. It looks exactly like that.</p>
<p>The good news: I was lying down and not standing with my neck craned over to avoid hitting the bin. The bad news: I had to remain motionless for the next half hour.</p>
<p>Having removed only essential items &#8212; eye glasses, wallet and belt (I didn&#8217;t bother wearing my ring and watch) &#8212; I was fully dressed. When the machine was turned on I got to experience what mostly felt like slight tugging and small static shocks dancing around the rivets on my Levis. That was pretty cool.</p>
<p>Then the noise started. The best way I can describe it is a bad haunted house. You&#8217;ve been to those, yes? The ones where they try to scare you with intermittent loud noises &#8212; someone banging on the walls with hammers, klaxons sounding periodically. Except in this case they hadn&#8217;t quite worked out that it is scary only when intermittent. If you bang continuously and leave the klaxon running its not scary, just really annoying. In fact, as the tones changed and moved about, I had to keep myself from laughing at the absurdity of it.</p>
<p>And loud. I can&#8217;t begin to tell you how loud. Over-the-top loud. Have you had fire drills in your building? With the really annoying electric beeping? Its like that. With someone hammer on metal. And occasionally sounding an air horn 2 feet away. I mean, forget waterboarding, just put detainees in an MRI for a really comprehensive exams. I guarantee, whom ever invents an MRI that is half as loud will make millions. And the current models will ensure National Security.</p>
<p>After a half hour of torturous, silly noise, I was free. A small headache and a large cache of images in hand I was headed home. I must say that flipping through the films is pretty cool. (Yes, film, not CD. My doctor apparently prefers the films.) And while I&#8217;m not expert, in looking at the back portion of my shoulder joint there seems to be a bit of something poking out the back that doesn&#8217;t look quite right.</p>
<p>We&#8217;ll see what the expert says in a couple of weeks.</p>
<h3>Update</h3>
<p>(3/13/2009)<br />
The doctor&#8217;s review of the MRI concludes that there is a minor anterior tear or two. For now he has proscribed physical therapy. In a couple of months we&#8217;ll re-evalutate.</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/mri/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Questions from a 3 Year Old</title>
		<link>http://tjameswhite.com/archives/questions-from-a-3-year-old/</link>
		<comments>http://tjameswhite.com/archives/questions-from-a-3-year-old/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 15:07:50 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Life and Things]]></category>
		<category><![CDATA[Olivia]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/archives/2009/01/questions-from-a-3-year-old/</guid>
		<description><![CDATA[
How does a pickle live on the Earth?
How does an eyeball go for a walk?
How does a lightbulb eat?

]]></description>
			<content:encoded><![CDATA[<blockquote>
<p>How does a pickle live on the Earth?<br />
How does an eyeball go for a walk?<br />
How does a lightbulb eat?</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/questions-from-a-3-year-old/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Raising a Child with Computers</title>
		<link>http://tjameswhite.com/archives/raising-a-child-with-computers/</link>
		<comments>http://tjameswhite.com/archives/raising-a-child-with-computers/#comments</comments>
		<pubDate>Mon, 24 Nov 2008 01:19:58 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Olivia]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/archives/2008/11/raising-a-child-with-computers/</guid>
		<description><![CDATA[While looking through our Atlas of the World this morning, I pointed out a beautiful satellite photo of Mt. Etna. &#8220;Look Olivia, this is a volcano,&#8221; said I. &#8220;What&#8217;s a volcano?&#8221; said she.
We then spent the next &#189; hour on YouTube looking at volcano eruptions.
Having instant internet access and rich media sites helped her understand [...]]]></description>
			<content:encoded><![CDATA[<p>While looking through our <cite>Atlas of the World</cite> this morning, I pointed out a beautiful satellite photo of Mt. Etna. &#8220;Look Olivia, this is a volcano,&#8221; said I. &#8220;What&#8217;s a volcano?&#8221; said she.</p>
<p>We then spent the next &frac12; hour on <a href="http://www.youtube.com/results?search_query=volcano+eruptions&#038;search_type=">YouTube</a> looking at volcano eruptions.</p>
<p>Having instant internet access and rich media sites helped her understand a volcano better than I was able to describe it, and we had a great bonding experience watching lava flow.</p>
<p>Thank you 21st century.</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/raising-a-child-with-computers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>On The Big Three</title>
		<link>http://tjameswhite.com/archives/on-the-big-three/</link>
		<comments>http://tjameswhite.com/archives/on-the-big-three/#comments</comments>
		<pubDate>Fri, 21 Nov 2008 01:16:19 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Automotive]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/archives/2008/11/on-the-big-three/</guid>
		<description><![CDATA[Do the U.S. automakers deserve a bail-out? No.
Should they get a bail-out? Yes.
Ford, Chrysler and GM have had plenty of time to retool and change their product line ups. They have refused to do so and now they are paying the price. Simply put, they don&#8217;t produce cars that many of us want. Trucks? Yes, [...]]]></description>
			<content:encoded><![CDATA[<p>Do the U.S. automakers deserve a bail-out? No.</p>
<p>Should they get a bail-out? Yes.</p>
<p>Ford, Chrysler and GM have had plenty of time to retool and change their product line ups. They have refused to do so and now they are paying the price. Simply put, they don&#8217;t produce cars that many of us want. Trucks? Yes, they produce plenty of those and the rising gas prices have squashed sales. Since it takes the automakers years (on the order of 5) to develop a new car, they are stuck and in trouble.</p>
<p>This is the path they have chosen and should pay the price &#8212; Chapter 11.</p>
<p>However, the financial industry also created their own problems by funding, buying and selling bad mortgages. The housing bubble was not something that happened out of the blue, those in the mortgage industry knew what they were doing.</p>
<p>That is the path they chose and they were given $700 billion to fix it.</p>
<p>The precedent has been set: we are bailing out bad decisions by the banks; we should then bail out the bad decisions of the auto industry.</p>
<p>When we look at the possibility of nearly 3 million people out of work, we have to do something. Congress is right to demand a solid plan from the auto makers before any money is handed to over.</p>
<p>As for the CEOs, I have no sympathy for them. They shall not hurt no matter what happens. I only respect one of them: Mr. Mullaly at Ford. His salary is an obscene $22 million <strong>per year</strong>, however, this year he has waived that and is only being paid $1. When asked by Congress if they would do the same, Mr. Nardelli (Chrysler) and Mr. Wagoner (GM) said no. Gentlemen, that is the wrong message to send to those from whom you seek money.</p>
<p>In the end I think the auto industry will be much leaner, more efficient and cost-effective in the future. I just don&#8217;t know when that future will arrive.</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/on-the-big-three/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
