Turns out on your birthday ol’ Google throws up a nice logo for you.

Google TV’s website is now live. Check out the tour and videos.

Link

Cubescape was developed by Cameron Adams

The interface for IE9 is quite streamlined, less chrome more web. I cant help but feel they might be taking a page from Firefox 4′s book, which could lead to a race to the finish line on a ‘who gets it out first came up with the idea’ race. Regardless, competition fosters innovation and we all win in this case.

I’m most pleased with the support for HTML5 standards and CSS3 support. The Firefox nightly builds are constantly implementing support for newer features (border-radius most recently) and Microsoft is making no excuses here. The IE9 test drive page is filled with examples of their support of modern web standards. A far shot from Chrome’s experiments, but a noble effort.

What does this mean for the web? It means that developers will now have support of the world’s #1 browser in the fight to transition to universal web standards. It means consumers will be able to view richer more compelling content. It means Microsoft has finally grown up.

Here are a few links for you to get set up.
At the time of this post, you need the Beta version of Chrome to use extensions.
Chrome Beta
Delicious Extension
Syncing in Chrome

If you need to use a 24 bit PNG in IE6 and want it to work, you’re going to need a little help. First, start by creating a new stylesheet just for IE6, call it ‘f**kYouIE6.css’ or whatever you’d like. Then call the css with the following code after all of your other CSS calls.

<!--[if lt IE 7]>
<link rel="stylesheet" type="text/css" href="css/ie6Blows.css">
<![endif]-->

Then, in your CSS file, add the following property to whatever class/id/object will be using the alpha layer transparency.

img {
filter: progid:DXImageTransform.Microsoft.AlphaImageLoader("images/button.png");
}

please keep in mind, that if you’re making a website for anybody other than yourself, the aforementioned naming conventions for css files is strongly discouraged.

Note: This is targeted towards Windows users; this will affect all browsers.

204. url += chiave + "=" + encodeURIComponent(valore) + "&"; //encodeURIComponent removes special characters that may break the key/value pair.

If you enter an apostrophe, it thinks the string has ended. If you enter an ampersand it thinks you’re joining a new key/value pair. So we just encode those (and all) values that would otherwise break the code.  Pretty simple solution to an annoying problem.

Further documentation: W3Schools – encodeURIComponent

The first step is to open up the rules window.

Go to Tools > Rules and Alerts…

Create a New Rule…

The example above is a completed rule, in order to achieve this you will need to select the conditions of your rule.

Since the incoming mail was sent to a discussion group, I simply select the ‘sent to people or distribution list’ option, and below in the Step 2 window I click the highlighted links to open up my Global Address Book and select the distribution list (or user if you like). Then select the folder I want it to go to.

Additional options are available in this process, such as marking the item as read. It is important to note that these will only work as client side rules, so if you’re on the road and you’re receiving emails via your mobile device, the rules will not apply unless you have this machine running and checking for incoming mail.

The button on your form should look something like this:

<button id="submit" onclick="validate(event); return false;">Send Email</button> the return false prevents the default action here

The validation code might go something like this:

function foo(evt){

evt = evt || window.event;

var theform = document.contactForm; //this is how I capture my form, by using the form's name

/* validation code can go here */

if (isvalid){ //a test i'm using based on validation requirements

theform.submit(); //will submit the form
}

//the following test will cancel bubbling and default actions across the form, we use this for IE.
if (evt.stopPropagation)

evt.cancelBubble = true;


}

Essentially what you’re doing is stopping the browsers natural reaction to an event, such as clicking the submit button on the form and letting it run through your validation code. The added lines at the bottom prevent certain browsers from continuing on with the default actions even though you’ve coded return false; in your button click. Thanks Internet Explorer.

This is some knowledge dropped on me by my good friend Lawrence. Check his site out for some other useful tips.