Hiding Styles from IE 6

It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors.

In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this:

div#nav { width: 150px; margin-left: 20px; }

This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far.

So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read:

body > div#nav { width: 150px; margin-left: 20px; }

Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS:

#nav { width: 150px; margin-left: 10px; }

The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

Hiding Styles from IE 6

It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors.

In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this:

div#nav { width: 150px; margin-left: 20px; }

This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far.

So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read:

body > div#nav { width: 150px; margin-left: 20px; }

Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS:

#nav { width: 150px; margin-left: 10px; }

The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

Hiding Styles from IE 6

It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors.

In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this:

div#nav { width: 150px; margin-left: 20px; }

This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far.

So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read:

body > div#nav { width: 150px; margin-left: 20px; }

Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS:

#nav { width: 150px; margin-left: 10px; }

The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

Hiding Styles from IE 6

It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors.

In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this:

div#nav { width: 150px; margin-left: 20px; }

This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far.

So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read:

body > div#nav { width: 150px; margin-left: 20px; }

Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS:

#nav { width: 150px; margin-left: 10px; }

The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

Hiding Styles from IE 6

It's actually really easy to hide styles from IE 6 but make them visible to standards compliant browsers. Use child selectors.

In one design I built, I created a two column layout that required margins and padding. This meant that I was hitting the box model differences when I viewed the page in IE 6. My first CSS style sheet for Firefox included a line like this:

div#nav { width: 150px; margin-left: 20px; }

This made the page line up perfectly in Firefox and Safari, but in IE the nav column was pushed over to the right too far.

So, I converted the line to use child selectors. The #nav div is a child of the body tag, so I changed the line to read:

body > div#nav { width: 150px; margin-left: 20px; }

Of course, doing this made the #nav div lose all it's properties in IE, so I needed to add in some IE styles to get IE 6 looking okay. I added this line to the CSS:

#nav { width: 150px; margin-left: 10px; }

The placement of this line of CSS is important if my page is still to look good in Firefox and Safari. The IE line needs to come first. Firefox and Safari will read that line and then it will be over-ridden by the body > div#nav selector lower in the document. IE 6 will read the first line and set the styles. It will then ignore the child selector, as it doesn't recognize them. When IE 7 comes along, it will act like Firefox and Safari.

By designing for a standards-compliant browser first, and then modifying your CSS to support IE's quirks, you spend a lot less time fiddling with the design and a lot more time

Tips on Removing
the Caffeine from Quality Tea

Approximately 80% of the caffeine in
tea is released during the first 30-seconds of steeping, therefore to
remove most of the caffeine from any tea simply

1) Pour boiling water over the tea leaves

2) Allow the leaves to steep for 30 seconds

3) Pour out the brew, saving the steeped leaves

4) Re-steep the same leaves with more boiling water for the recommended
steeping times.

Highlight converts source code to formatted text with syntax highlighting.






• Coloured output in HTML, XHTML, RTF, TeX, LaTeX and XML format


• Supports 120+ programming languages


• Includes 40 colour themes


• Platform independent


• Customizable and easy to use

Rissoles of the Gods







• 1 kg mince (good quality beef or a half-and-half mix. Lamb or pork mince is good. When I was a kid we'd combine beef with kangaroo mince. Grass fed beef is always better than grain fed)


• 2 eggs


• ½ cup breadcrumbs--I always go for the most retro packaging


• 3 tablespoons Clive of India Curry Powder


• 1 large onion, finely chopped. You might want to brown the onion first, but I prefer it crunchy


• 1 carrot, grated


• Lea & Perrins Worcestershire sauce


• Tomato paste/tomato sauce/ketchup, around ½ a cup


• Liquid Smoke (very optional)


• Grated parmesan cheese, optionally blue cheese. I don't know if this really does anything much, beyond increasing the fat content


• Kikkoman soy sauce, just a little


• Pepper


• garlic (if you can be stuffed)


• Jane's Krazy Mixed-Up Salt, which is great on anything


• plain flour (for later)






1. Brown the meat and the onions if you prefer everything grey and soggy. It's a personal preference, and I prefer my meat a little red..


2. Mix everything (except for the flour) together in a large bowl. Traditionally you should use your hands, and it's much more fun doing it that way.


3. Let the covered mixture sit for a couple of hours in the refrigerator. Even leave it for a day or two. The rissoles will only taste better.


4. Put some seasoned flour in another bowl. Shape the rissoles with your hands so that they are each about the size of a hacky sack, flatten them out a bit and roll them in the flour.


5. Stick the rissoles in a hot frying pan with a bit of oil in it. Alternately, put them on the barbecue. Cook them until they're crunchy on both sides. A bit of charcoal never hurt. Best that they're still moist and red on the insides.


6. Put the cooked rissoles on some paper towels on a plate to soak up any excess oil.


7. Serve with steamed vegetables and mashed potatoes and gravy. Warning: the flour coating will soak up most of the pan juices, so you might be better off using a ready-to-eat gravy mix.


8. Any leftover rissoles should be eaten cold over the next few days in sandwiches made with tomato chutney. Bliss!



Obviously, cooking rissoles isn't an exact science. You can skip ingredients and add others according to your own predilections. But this recipe should serve as a decent introduction to the exciting World of Rissoles.

My proposed steps for the Emotional Getting Things Done system:

1. When you begin the system for the first time, write down every
emotion that still plagues you from your past (e.g. the death of a
loved one), problems that are on your mind about current events or
events in the very near future (e.g. worrying about failing that test
this week), and problems in the forseeable future (e.g. dilemmas over
how to spend your life). The examples that I listed are all bad
feelings, but the same should go for happy ones: you are included in a
promising opportunity, you just lost 30 lbs, etc.

2. During your day, whenever a meaningful emotion hits you, right it
down immediately! "Gee, I sure am pissed that my best friend Billy
would say something about <insert person>. I'm going to write
down my anger so as to not let it fester and ruin my
happiness/productivity." The Hipster PDA would be perfect for this.

3. Process: Look through all of your emotions and decide which are
good and which are bad. The good emotions need no next step - throw
them away or file them (haha, yeah right). The bad ones need one more
step:

4. Resolution or next action: Write down how these emotions could be
resolved. For example, if I were processing "I'm incredibly pissed at
myself for failing that test," I'd write down, "It's ok. It's only one
test. I'll just study harder next time, and I'll be on top of the world
again."

5. If a bad emotion takes physical tasks to resolve, then add those
steps to your GTD inbox and process them as a normal task. For example,
maybe a feeling of guilt could be resolved by calling someone and
apologizing - or just talking to a person about your problem in
general. Or, maybe you're feeling lonely; schedule some time to spend
time with friends!

I have no idea if this will work, but it seems very logical to me.
The same idea applied to GTD also applies to this: get things out of
your head. Productivity and happiness? That's something I'd love to maintain on a regular basis. It's the GTD equivalent of a journal.

I have recently come up with a metadata markup system that evolved out of the “dash/plus” system that I use for action items in my Pocket Moleskine. I will try to describe it as best I can with text but it is better viewed so I have included a link to a picture:

- (Dash): Undone Action Item.

+ (Plus): Done Action Item.

<- (Right Arrow): Waiting - i.e. for another action).

-> (Left Arrow): Delegated (with a note to whom and the date).

^ (Triangle): Data Point.

O (Circle): A circle around any of the above means that it has been carried forward, moved to another list or otherwise changed status - i.e. a “Waiting” item has now become an Action Item elsewhere (with a note about where that item has gone).

How, then, does one go about creating a page from a content-centric point of view? Let’s compress it into a simple step-by-step list of instructions:





1. Using a text editor, write the content of the document; i.e., every piece of information that will appear on the page.


2. Add semantic markup to the content, marking up paragraphs, lists, tables, emphasis, etc. Also add the ‘formal’ parts of the HTML document: the DOCTYPE declaration, the HEAD element, BODY tags, etc. (This step is often combined with the previous one.)


3. If appropriate, replace parts of the content with images that illustrate or complement the text. Use the replaced text as the ALT attribute for each image. Add any decorative images (those that illustrate the article, but do not convey any relevant information). Use an empty ALT attribute (alt="") for those images.


4. Create the CSS style sheet. Start with generic rules, i.e., rules that use simple element type selectors. Specify rules for basic things like font family and line height, preferably on the HTML element. Specify explicit margins and padding for all element types, since the defaults differ between browsers.


5. Add rules for the page layout, using floats and/or absolute positioning. Make sure to use relative units (em or %). At this stage, it will usually be necessary to add ID and CLASS attributes to the markup. Most layouts will also require a few wrapping DIV elements to group page components.


6. Add the remaining CSS rules that will handle things like background images (which may be created from a comp), colours, borders, etc. If you’re styling links, don’t forget the a:focus pseudo-class, which is vitally important to users who navigate by keyboard. (Internet Explorer or “IE” doesn’t support it, but incorrectly implements a:active for keyboard focus instead.)

• Initial visibility: Is all key information visible above the fold so users can see it without scrolling? This is a tradeoff between how many items are shown vs. how much detail is displayed for each item.
  
• Readability: How easy is it to read the text in various columns, given their allocated width?
  
• Aesthetics: How good does your page look when the elements are at the proper size and location for this screen size? Do all the elements line up correctly -- that is, are captions immediately next to the photos, etc.?