[pmwiki-users] Skin problem with wikitrail
peterkayatwork at yahoo.com
Sun Apr 23 11:54:50 CDT 2006
> Sunday, April 23, 2006, 3:18:08 AM, Peter wrote:
>> Is there a way for a Skin to update PmWiki/GroupHeader? Being able to
>> make a Skin isn't very useful if the default installation has some pages
>> that don't play well with the skin... (dark background = light
>> foreground, which causes problems - I can't ready white on yellow :-) )
>> Or would my skin just have to have instructions "Go to
>> PmWiki/GroupHeader and start making these changes"?
> No, you need to edit Pmwiki.GroupHeader yourself.
> GroupHeader is a normal wiki page, with the special quality that its
> content is included on the top of every page in the group.
> That is the reason it is useful to put wiki style definitions there,
> which will have an effect for all pages in the group 9like the trail
> used on pmwiki documentation pages).
That does present problems for a Skin designer.
I would think the more appropriate behavior would be to give classes to
these things, and specify the appearance in the Skin's css.
The default installation seems to have:
%define=trail bgcolor=#eee block%
%define=note font-style=italic color=green%
%define=important block bgcolor=#fcc border='1px solid black' padding=5px%
%define=audience class='frame rfloat' font-size:smaller bgcolor=#ffffcc%
I'm guessing the "block" is something that couldn't be done easily in
css, but everything else could (and should) be classes.
> I think we need to document somewhere (related to skin changes
> perhaps) which of the default pages coming with pmwiki use any sort of
> color definitions for certain elements.
> Ideally these should not be in any page, but rather in css.
I'm not familiar with how PmWiki makes changes to its structure; if I'd
like to see this done, is the mailing list the appropriate place to
discuss it? Should I bring it elsewhere?
More information about the pmwiki-users