sugarenia.com

Sometime in the recent past, I recall myself registering to Windows Live Mail beta. Don’t ask me why. It was …impulsive.

To be frank, it was one of those “do-and-forget” situations. I’ve participated in hundreds of those. I register for betas and receive newsletters with product updates and web applications progress reports, and I always find myself wondering : when did I spend my time on that? I’m not looking down to anyone, mind you, but I guess I’m all too absent minded.

Windows Live Mail beta was one of those occasions. Thus, you imagine my fascination when I opened my cluttered Hotmail inbox one day to be greeted as “one of Hotmail VIPs”. Eh?

Apparently, I’m a Hotmail VIP member now. The joy!

OK, I merrily thought, let’s give a try to this bad guy. After registering for the new Yahoo e-mail service a few days ago, I even thought “Hey, I know! I’ll make a mini-review of both and I’ll blog it!” – btw, here’s a great way to convert your Yahoo! e-mail from Lifehacker.

My thinking-acting progress:

1. Shiny Orange Button, hm, bleh.
2. The little bugger is not even properly aligned. Pfft.
3. Let’s click it. *hover* Hey, why doesn’t my cursor change to hand? I hate this thing! Oh well..I’ll click it either way.
4. *click* *click* No click. Not clickable? Weird. Let’s scan the e-mail for a similar link.
5. (some minutes later, after scanning the e-mail, clicking on all relevant links, searching around their site et cetera) That’s it, I quit. And on top of that, I’m SO blogging it.

The Shiny Orange Button

Apparently, Hotmail does not know how to manage their e-mails. That so figures.

Maybe it’s just a well concealed spam? I don’t know. Maybe I’m too naive a user? Maybe.

hotmail, windows live mail

Well, apparently, Web Standards are working like a charm in order to build you a sexy profile.

I made a brief research on that, with seven names that came directly to my mind while thinking “Web Standards”. Check these hotties out, in no particular order:

If you don’t know them, from left to right : Andy Budd, Cameron Moll, Simon Collison, Molly E. Holzschlag, Jeffrey Zeldman, Dave Shea, Dan Cederholm.

Standards make you hot as an oven-hot bun, don’t they?

P.S.1. Apparently, this is a fun topic. I’m neither related nor affiliated to any of the above persons. However, I respect their work immensely.
P.S.2. No girlfriends/wives, boyfriends/husbands were harmed during the making of this post. I hope noone is offended.
P.S.3. Feel free to nag me to add yourself.

andy budd, cameron moll, simon collison, molly holzschlag, jeffrey zeldman, dave shea, dan cederholm

The Problem

If you’re like me, you often use Macromedia Dreamweaver 8 to quickly edit the CSS you create (on a break from excellent TopStyle Pro from Bradbury Software).

Dreamweaver offers a good deal of code hints, which can be particularly handy when authoring CSS. One of the attributes I (and by I, I mean everyone) use the most is the “padding” one. Everyone loves paddings, no? Paddings are cutier than margins.

Since the padding attribute does not have specific values that can be applied to it (like in “font-size: small” for example), Dreamweaver automatically displays only “inherit” as its code hint. In addition, I (and by I, I hope everyone) extensively use tabs to indent my code.

So that’s what happens : you write “padding:”, you press Tab, “inherit” is the default option, you press Tab again (because one can never be enough) and voila! Dreamweaver decides that padding: inherit looks better on your CSS document, and writes so.

This has repeatedly led me to a) crying out loud b) ripping my hair off c) making ridiculous finger acrobatics with the arrows and Tab buttons to avoid auto-completion, adding up to the pain of my poor, strained wrist. This had to stop. This had to stop without disabling auto-completion.

The Solution

Thank God for Dreamweaver XML configuration files. A little search around Dreamweaver live docs, and the answer is right there.

Browse to %yourDWfolder%/Configuration/CodeHints folder. There you’ll find a single XML file called CodeHints.xml (inspired, no?). If you’ve never concerned yourself with XML in the past, fear not, we will not go deep. So, open the file in your favourite editor (hey, maybe DW will do – haha). Around line #5363, you’ll find the following lines :

Click on the image to enlarge

See the evasive “inherit” menu option? Good. So now we have two options : either we delete the thing, forget about inherited padding and go to sleep, or we burn with remorse and leave the darn thing, only to add another option and avoid the auto-selection because it’s the only option. I’ll show you how to do both, but it’s really up to you.

Don’t forget to make a copy of your file before you edit it, so you’ll be able to get it back if things go terribly wrong (they won’t, but do it anyway).

1. Delete “inherit” option : For all the “padding” attributes (padding, padding-top, bottom, left and right) delete the line that lies below. Also, because we are XML monsters, since the tag is empty, delete the ending tag and add a forward slash (/) just before the end of the menu line (before the closing >). This should leave your padding lines look like these :
   
   Click on the image to enlarge

2. Add a foo option so that “inherit” is not automatically selected: Copy the line of “inherit”, and paste it just below it, changing label=”inherit” to whatever you like. Like label=”inherit2″ or label=”foo” or label=”George”. Do that for all the padding lines, and your XML file will look like something like this:
   
   Click on the image to enlarge

Save and close the file, restart DW, and never worry about auto-inherited padding anymore.

P.S. If you’ve got another way to deal with this particular problem, I’d be thrilled to know.

dreamweaver, code, CSS, code hints, customization