Arise and walk!

• I can't stop listening to the Where the Wild Things Are soundtrack, and I can't wait to see the movie tonight! #WildRumpus #fb #

Powered by Twitter Tools

• I'm looking forward to seeing locals @COOPAleWorks @mustangbrewing @batteredboar @ChocBeerCo @ ART ON TAP tonight! #DrinkLocalBeers #

Powered by Twitter Tools

• I'm about to see @TheDecemberists at Cain's Ballroom with my sweet girlfriend and I can't wait to hear the Hazards of Love set! #
• @colinmeloy and @TheDecemberists that HoL set at Cains was spectacular! #

Powered by Twitter Tools

When I power my workstation on I have come to expect a short delay as the BIOS and OS load (it is a older and underpowered system). What I can't stand is the need for Windows Update to delay the load of the login screen to complete the installation of updates.
I can understand that some updates need a re-boot to complete - when I select the 'Update and Shutdown' option, I expect that the computer should do whatever it has to to apply those updates.
When a user turns a computer on, the system should be ready.
Twice in the last two weeks I've had to boot-up my workstation to solve a problem at work, I've had to wait for updates to be applied.
My biggest fear regarding this issue is that the practice will continue in future versions of the OS, and possibly spread to older versions via service packs. As I said, the OS should do what ever it needs to once the command to update and shut down has been given.
Please post a comment if you have any idea how to change this behavior.

I haven't mentioned it here before, but shortly after the native SDK for the iPhone and iPod Touch was announced, I purchased a Touch.

Within a few days I had applied the original Jailbreak. I'm now running the latest firmware (thanks to ZiPhone).

The Touch is the best electronic device I've ever owned. I love it - the only problem I have with it is that I don't have Wi-Fi access everywhere, so a iPhone would certainly be a bonus. I'm going to wait until later this summer, expecting a hardware update by then.Now that the SDK has been released I'm thinking hard about what software I'd like to see, so I can begin building it now.

The biggest problem that I see with the SDK is that the apps will not be allowed to run in the background - that means of course that my favorite app, MobileScrobler, probably won't work.

So, maybe the Jailbreak community will still exist.

More posts when I decide what to build...

...a supprise to read the news that Indian automaker Tata has entered a bid for Jaguar and Range Rover from Ford.With the countries mutual history, I'm sure that Range Rover (if not Jaguar, too) is higly regarded. It will be intresting to see how that develops and what the plans they have are.(Via Winding Road.)

Yesterday, the day that Leopard was released for Macs, was also my white MacBook's eleven month anniversary. What better way to celebrate than to get the upgrade and a free shirt!

So on my way home I stopped by the Apple store near the house at 6:20 and found a short line stretching about 3 storefronts. The line moved fast and I had a good time talking to my neighbors about Macs and iPods.

Inside the store was packed, I saw at least a dozen black MacBooks checking out at once. I got a t-shirt and a copy of Leopard and I was back to my car 25 minutes later.

Back at home I backed up, tested the backup, rebooted, installed, waited about an hour, it rebooted, I logged in, I waited about another 10 minutes — and then, it finally booted.
I really like what I see so far. I have had the System Preferences app crash a few times, but over all I'm happy with all the changes.

I'd like to point out that Michael Tsai, creator of SpamSieve (my spam tool of choice) sent out an excellent email announcing his products compatibility with OS X and providing very simple instructions on how to re-enable the plugin after the update. Thanks, that went just as easily as described.

The surprise feature that I love the most is the updated Bluetooth File Exchange app.

I was able to browse the memory stick on my W810i and have been transferring the files (hundreds) for the last 20 40 60 minutes! In that time I've had two phone calls too. Once I get a folder that is in sync I'll automate the process and have it upload to my flicker stream too.
If you've got a Mac, get the update. If you don't have a Mac get one now — its better than ever.

The Problem: I don't like using the ASP:Button control on the ASP.Net Applications that I build. Mainly because I have little control over how they appear and act. The ASP:ImageButton is better, but it requires that I (or someone) make images with the text required - and when going international that work snowballs quickly.

The ASP:LinkButton is my control of choice. I can use CSS to make rollover and hover states, use what ever text I'd like. Out of the box, as long as IE is the browser everything works - but as soon as you try to submit a form with a LinkButton as the default button in FireFox, the form just reloads and any values that were input are lost.

The Investigation: I found several posts and examples, but most of them were for extending the ASP:Button or ASP:ImageButton controls. I also noticed that they were trying to submit the form via a PostBack method and with the LinkButton it just wasn't working.

The Solution The answer was right there in the page's source as sent to the browser. The LinkButton control gets rendered as a link [A] to the browser. All you need to do to cause the button to fire is go to the address in the HREF.

The Code: Add this code to a SCRIPT block in your MasterPage (or better yet, to a seperate .JS page that is linked to your MasterPage).

function DefaultButtonKeyPress(evt, thisElementName) {
if(evt.which || evt.keyCode)
{
if ((evt.which == 13) || (evt.keyCode == 13))
{
// alert('post back href: ' +
document.getElementById(thisElementName).href);
location =
document.getElementById(thisElementName).href;
return false;
}
}
else
{
return true;
}
}

All that code does is send the browser to the location that you'd go to if you clicked the link, but only if you hit the ENTER button when in a TextBox that calls the JavaScript method.

To get your TextBoxes to call that method, you need to add the following method to your project somewhere. (I have a PresentationLayerTools.vb class where I put all this code, you might like it somewhere else).

Public Overloads Shared Sub DefaultButton(ByRef TextBox As System.Web.UI.WebControls.TextBox, ByRef LinkButton As
System.Web.UI.WebControls.LinkButton)
TextBox.Attributes.Add("onkeydown", "DefaultButtonKeyPress(event, '"
& LinkButton.ClientID & "')")
End Sub

All that code does is add a OnKeyDown event handler to fire the JavaScript method above to the specified ASP:TextBox. The method listens for KeyDown events, if if finds one, it checks to see if the Key you pressed was the ENTER - if it is then it send the browser to the location of the ASP:LinkButton's HREF attribute (which, buy default is a call t another ASP.Net controlled JavaScript method that fires off a PostBack; I'm not sure what all else it does, but it works so I'm happy).

Finally, you need to add the following to the code behind for your pages to tell ASP.Net to execute the DefaultButton method above. I suggest doing it during the page's PreRender event; but it could go other places too.

Protected Sub Page_PreRender(ByVal sender As Object, ByVal e
As System.EventArgs) Handles MyBase.PreRender
Page.Form.DefaultButton = LinkButtonLogOn.UniqueID
PresentationLayer.Tools.DefaultButton(Me,
TextBoxEmail, LinkButtonLogOn)
PresentationLayer.Tools.DefaultButton(Me,
TextBoxPassword, LinkButtonLogOn)
End Sub

Please note that you have to add a call to the DefaultButton method for each TextBox you have on your form that you want to submit the form on.

The Conclusion: I hope that makes sense and works for you, it took me a half a day of banging my head as I searched the Web for a fix. This morning after a nice nights rest the answer was obvious; but because I couldn't find any other similar suggestions I figured I ought to post this to help someone else out.

This code has been tested with: IE 7 and 6 on Windows Server 2003 and Windows XP, FireFox 2 on Windows Server 2003, FireFox 2 on OS X 10.4.10, and Safari 2 on OS x 10.4.10. If you try it on other platforms please let me know how it works!

Build this car! That is what a rally inspired street car should look like, and the best way to compete with the upcoming Evo X.

(Via Jalopnik.)

The Time Is Nigh: NOW Watch is Always Right.

(Via Gizmodo.)