#1 clean up crappy code

[mrdyg]

Run emacs 'whitespace-cleanup'.
Convert indentations.
Organize a directory structure.
All output written to the browser should validate against XHTML 1.1 Transitional (xtrans).

PHP Guidelines: http://pear.php.net/manual/en/standards.php

For CSS, indents should be 4 spaces, all selectors lower case. In lists, selectors should be on separate lines. All properties on separate lines.

#id,
.class,
element.class child {
property1: value;
property2: value;
}

For HTML output, indents should be 2 spaces, but this is a very loose rule. Use proper doctype. All elements should be written in lower case and be properly closed (xtrans policy).

--- In whisper3@yahoogroups.com, "Rob Wiltbank" <wiltbank@...> wrote:
> Here's my preferences for the record.
>
> function testFunction($var1, $var2)
> {
> for($i = 1; $i < 10; $i ++)
> {
> echo 'This is a text message.';
> }
> }
>
> Using tab characters for tabs so when other developers open up the
> code in their preferred IDE, the tab space will be set to their
> personal preference. ANSI C-style braces. Camelback naming for
> multiple word functions... maybe some variant of hungarian notation
> for variables if we want to go that far.