#1 Skin implementation

[Haryon]

Pick the design where there is only one skin possible
per page, and it's accessible as procedure (class
method).

class Twig_TextField {

function Twig_TextField() {
....
$Skin->getResourceFor('textfield.cssclass');
....
}

}

[Haryon]

Logged In: YES
user_id=431564

Implementation change on the way HTML is outputed will
lead to different handling of skins.

At the moment there are 2 basic approaches :
1- one xsl per skin
2- skins are simply css+files in a directory, where filenames
are all the same, but each skin is in a different directory. xsl
file is skin indepedant.

1/ maximum gives flexibility, but javascript for validation or
such will be duplicated :( much more work.
2/ minimum flexibility, will have to resort to using do stuffs
like : tables uses images for borders in every skin... no way
to make heavy and light pages with skins :(

[Haryon]

Logged In: YES
user_id=431564

Architecture changed to XML/XSL. Skins are XSL pages.
Only Skin picking by the user (or user barony race) is not yet
implemented.