[pmwiki-users] Edit template to use for documenting a new skin?

tamouse mailing lists tamouse.lists at gmail.com
Sun Sep 16 17:03:26 CDT 2012

On Sun, Sep 16, 2012 at 10:07 AM, Petko Yotov <5ko at 5ko.fr> wrote:
> tamouse mailing lists writes:
>>      1101  2012-09-15 14:58   skin.tmpl
>>       660  2012-09-15 13:08   skin.php
> It will be a fraction of a second faster if you name these mouseskin.php and
> mouseskin.tmpl (if "mouseskin" is your $Skin name) rather than "skin.php".

Okay, I'll rename them.

>>       603  2012-09-15 13:14   wikilib.d/Site.GroupFooter
>>      2352  2012-09-15 13:14   wikilib.d/Site.GroupHeader
>>       947  2012-09-15 15:54   wikilib.d/Site.SiteActions
>>      2491  2012-09-15 13:14   wikilib.d/Site.SiteBrand
>>       869  2012-09-15 13:14   wikilib.d/Site.SiteFooter
>>      2149  2012-09-15 13:14   wikilib.d/Site.SiteHeader
>>       396  2012-09-15 13:14   wikilib.d/Site.SiteNews
> You should note that most "generic" page names up here can already contain
> some text in an existing wiki. In such a case, noone will ever see the
> templates you provided. Some skin authors have chosen to have specific page
> names, like wikilib.d/Site.MouseSkinSiteHeader.

Ah, yes, I can foresee a problem with that... which I guess begs the
question: how much should be done in the template, and how much should
be done via wiki pages. I've been enjoying being able to mutate things
quickly via wiki pages and prefer doing that to mucking with the
template. The template is really pretty basic, and the richness comes
from the wiki pages that populate the elements.

> I really don't recommend relying on pages GroupFooter or GroupHeader being
> unused in a remote wiki.

I was avoiding setting $GroupHeaderFmt and $GroupFooterFmt in the
skin.php file to allow the admin to set these differently than what I
might choose. I'm rethinking this now, but would appreciate some
guidance on this...

More information about the pmwiki-users mailing list