<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
The context for this is that for all my PmWikis, I create a skin,<br>
ie in <tt>config.php</tt> use <tt>$Skin = "ttcnew";</tt><br>
This means of course that I don't alter the default "pmwiki" skin
template or css file.<br>
<br>
In fact the /ttcnew/pmwiki.css has as its first line<br>
<tt>@import url("/pmwiki/pub/skins/pmwiki/pmwiki.css");<br>
</tt>This means I can relay, by and large, on updates to the default
skin's css working properly without my aving to reintegrate them.<br>
Also my CSS file is smaller, and only captures the customisations I
need.<br>
<br>
Now I don't know about other admins,<br>
but my preferred approach to customisation is to use css<br>
(rather than code or template changes)<br>
through the skin's pmwiki.css.<br>
<br>
As long as most elements in a page are given a class<br>
(not an id please - sometimes we want to reuse them)<br>
and appropriate bracketing (eg span or div where there is not element
already)<br>
this works a treat.<br>
<br>
But from tie to time you will see requests asking for a class to be
added to an element,<br>
or, like this one, the ordering to be changed so the "hard coded" css
in the wiki page is more amenable to the influence of the skin's css
file.<br>
<br>
Consequently I would prefer to be able to override "in page" styles to
get the look and feel I am after.<br>
<br>
thanks again<br>
<br>
Simon<br>
<br>
<br>
Patrick R. Michaud wrote:
<blockquote cite="mid20051207220823.GL26817@host.pmichaud.com"
type="cite">
<pre wrap="">Repeating some of my comments from the PITS entry:
On Thu, Dec 08, 2005 at 07:04:13AM +1300, Simon wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> 1) Include the pmwiki.css file after the page specific styles ie in the template
<!--HeaderText-->
<link rel='stylesheet' href='$SkinDirUrl/pmwiki.css' type='text/css' />
instead of
<link rel='stylesheet' href='$SkinDirUrl/pmwiki.css' type='text/css' />
<!--HeaderText-->
This will allow the pmwiki.css styles to override the styles included in the page.
</pre>
</blockquote>
<pre wrap=""><!---->But this also makes it much harder for an admin to override the styles
in pmwiki.css. Beyond that, I can't imagine any situation where we would
want the pmwiki.css styles to override the styles included in the page.
</pre>
</blockquote>
</body>
</html>