[daisy] [skin2] Poll for participation and input

[Vincent Mouton]

My first input (I deleted the mail trail too soon). There's more in my head
somewhere, but this has been cooking all evening, night and morning. So
while it's still fresh, I launch it.


- I'm personally not so fond of adding a id to the body tag, for each
document. In real life (or rather, in the daisy sites we skinned), we
defined specific classes to the body tag for the homepage, and nothing for
everything else. More likely, one would like to style pages specifically
based on their DocumentType, so add a class to the body tag depending on a
DocumentType, rather than on a document id. I also think it is not wise to
link id selectors in the css, to document id's. What of one day you decide
to delete that document, and create a new one?

- some errors we got when skinning, or rather: some mistakes we made, was
cleaning the layout.xsl too much. Like removing all the dojo scripting,
etc... It would be better of the layout.xsl only contains the most essential
page elements: header, footer, nav, containers (like content containers),
language switch; and load external files like css, js, etc.; to that, one
could add calling specific stylesheets from layout.xsl, that do stuff daisy
needs (daisy nav, dojo scripts)

- just my input: how we structure our css files:

	screen.css
		layout.css
		tables.css
		forms.css
		microformats.css

	print.css

	A quick explanation: screen.css loads all other css files, and only
defines styles using tag selectors (how big and collored the hx tags are,
how a tags are rendered, 	....; layout.css positions main div elements
and contains, styles hx, a, span, lu, li, etc.. tags depending on their
container (a <a> in the content looks different 	than a <a> in the
navigation; tables.css and forms.css and microformats.css speak for
themselves

- one issues can easily be solved by using the above, quite generic and wide
used, structure: styling content inside the daisy editor. one could move all
html-tag selectors from the screen.css and insert it in a styles.css, and
one could replace the screen.css with a daisy.css like such:

	daisy.css
		styles.css
		daisylayout.css
		daisytables.css

	The styles.css defines styling of hx tags, a, ul, li, etc...
daisylayout.css styles the container divs for the stuff around the daisy
editor, the daisy nav; 	daisytables.css styles stuff like search results,
the recentChanges page, this to prevent the website's styling to alter that
table and make it unreadable; this 	requires all daisy layout elements
to have specific id's, classes, or combinations
	

- I'm not so fond of css frameworks. I find it much easier to control how
xhtml and css is structured

- One extra word about the phantom namespaces in the xhtml output, that does
not validate: this *is* an issue. Yes indeed, one could claim that the
requirements of the validator are over the top, but they are there, we have
to deal with them. making this work, would be marvelous. I do feel the pain
about the workload on this one, though.



That's it for now, I'll be adding more later. As we're now skinning 5 sites
in one, and have skinned 4 in the last year or year and a half.



Cheers,
v