Brion Vibber wrote:
wikistandard.css:
.exturl { display: none } /* redundant on screen */
print.css:
.exturl { display: inline } /* need in print */
html:
<a class="ext" href="http://blah/">foo</a>
<span class="exturl">(http://blah/)</span>
Yes, lynx and Netscape 4 with JavaScript disabled will see extra URLs.
Tough.
That would require some change in the page output code. But fair enough :-)
There is another problem -- it seems a bit daft to have to specify a
print version of the stylesheet of each skin.
We could use another LINK in the HTML HEAD for the print stylesheet, but
the problem is then that each skin has different elements that must be
hidden.
I think a global print stylesheet would be best, and to do that we'd
have to specify a basic page architecture common to all skins. This
doesn't need to be more specific than:
* all header content is in DIV id='head'
* all sidebar content is in DIV id='sidebar'
* all footer ... etc
A reorganisation like this might be easiest to do after we convert to a
template system using "smarty".
While on the subject of stylesheets, I've been pondering something else
lately.
Something like image-floating styles would presumably be the same in all
skin stylesheets -- at least the basics. (some future skin might want
flashing green border, who knows!)
Is it best to:
a) paste the same class into each skin stylesheet. Future skin
stylesheets must then ensure they begin from a template that has the
essential classes
b) create a "global" stylesheet of elements that work across all skins.
On UnrealWiki I went for option b). Particular skin stylesheets can
still add rules to those classes of course, but the core stuff, eg
"float:left;" is set in only one location.
But it does mean every browser downloads 2 stylesheets instead of 1.
Would this be a problem for our server?
if not, this is something I would like to implement.