Well there is a lot of 'good stuff' in PmWiki.css,
and of course from time to time it gets updated.
This 'good stuff' provides the much of the basis for any skin,
so rather than maintain the whole thing myself I choose to include it
override it where necessary,
or remove (some) references to its
Thanks Everyone for the tips, and sorry for the slip of the tongue with using
style instead off script. I got what I was looking for in the end, which was
disablemarkup(). It would be a slight nightmare to upgrade versions without
something like that. I'm in school again in Rome, so there is
To get your CSS to override existing CSS it will help if you change to,
as follows,
the order of these lines in your template.
!--HeaderText--
link rel='stylesheet' href='$SkinDirUrl/pmwiki.css' type='text/css' /
This ensures that your skin CSS overrides the pmwiki css
I believe that this
what are the best practices for disabling markup without replacing it? I have
had to edit the style sheets a few times.
Seth
-
No need to miss a message. Get email on-the-go
with Yahoo! Mail for Mobile. Get
Tuesday, March 6, 2007, 1:57:06 PM, Seth wrote:
what are the best practices for disabling markup without replacing it? I
have had to
edit the style sheets a few times.
To change css style definitions it may work (depending on the skin you
use) to simply add your custom css definitions to
are you saying that I should just create empty parameters, for example if I
wish to disable some of the standard markup used for italics or bold?
Or, for example, I changed to format of headings, but didnt want to break
everything, so I changed the standard parameters from being 1 exclamation
Tuesday, March 6, 2007, 3:35:26 PM, Seth wrote:
are you saying that I should just create empty parameters, for example if I
wish to
disable some of the standard markup used for italics or bold?
Or, for example, I changed to format of headings, but didnt want to break
everything,
so I
