In old-style HTML, tables had all sorts of attributes you could use to do things that are now done with CSS. This summary is my attempt at a quick-reference on how to translate the old style to CSS.

These are the chronicles of my adventure to find a way to easily install and maintain a MythTV front-end running atop a VIA EPIA ME6000 and a 1GB compact flash card as a hard disk.

This document assumes familiarity with the GNU/Linux OS, in particular, the Debian distribution. Furthermore, it is meant to be more of a resource of resources for those using Via's embedded platform. As such, little emphasis is made on the "how", but rather, the "what" and "where."

Please also note that this how-to is heavily under construction, so feel free to email me with suggestions, hints, tips tricks, questions, comments, queries, etc. I will do my best to get back to you

So why should we care? Because what people don't seem to realise is that if IE did things the same way as the other browsers, it would actually make web development much easier. Page code would be much cleaner and less bloated, more accessible. They would take less time to write, and in most cases would be cross browser compatible, usually without the need for hacks or detects. Web pages would be more likely to just work, and it would cost significantly less to make them.

This article describes the use of HTTP headers to control the caching of Web pages in Internet Explorer.

The Rollovers class presented here is an example of "unobtrusive Javascript" (see Google) for creating image roll-overs.

This article is intended for web developers who use remote procedure calls (RPC | Remoting | AJAX) to update portions of a webpage without having to reload the entire web page. Specifically, this article deals with a method I used to overcome the obstacle of Internet Explorer's browser-side caching of "javascript initiated" partial page updates.

A wrapper for XmlHttpRequest that supports forced caching on FireFox and forced non-caching on IE.

It is in the spirit of CSS that this article is written. There are hundreds of websites offering CSS tutorials, CSS examples, competitions, and showcases. There may be some that we are not aware of which are not displayed here, and if so, we encourage you to let us know in the Site Reference Forums.

With that said, we must offer a word of warning before going to any of these websites. These sites can become very addicting if you enjoy web design in the slightest way. Some of these sites link to literally hundreds of other sites which will catch your interest.

Now that the warning has been issued, we present to you a list of our favorite CSS websites.

Ever have trouble getting your Internet Explorer-specific Web applications to work with Mozilla? This article covers common issues associated with migrating applications to the open source Mozilla-based browser. You'll first learn basic cross-browser development techniques, and then develop strategies for overcoming the differences between Mozilla and Internet Explorer.

Edit in place (also called in-place editing) follows the axiom Alan Cooper calls "allow input wherever you have output". The combobox - a form element unfortunately absent from HTML - demonstrates this. In the same place where the current selection is displayed, the user can enter a value directly.

Although the XMLHttpRequest object might sound complex and different from any other JavaScript object you have ever used, it really isn't. A good way to think of the XMLHttpRequest object is as you would think of the JavaScript Image object. As we know, with the Image object you can dynamically specify a new URL for the image source without reloading the page. Similarly with the XMLHttpRequest object, you can dynamically specify a URL to get some server data without reloading the page.
The purpose of this article is to demonstrate through a series of baby steps just how easy it is to use the XMLHttpRequest object.

Now here's a dirty little secret: browsers aren't actually treating your XHTML as XML. Your validated, correctly DOCTYPE'd, completely standards compliant XHTML markup is being treated as if it were still HTML with a few weird slashes in places they don't belong (like <br /> and <img />).

Why? The answer is MIME types.