[Pmwiki-users] printable-page, flexlayout, and webmenu
Mon Aug 25 19:16:57 CDT 2003
My idea was also to provide a "style" argument for the url, to support
Later it could be mangled into PmWiki to pass it through, such if it was
once it will be there forever...
This makes me think, that it might be worth to have a list of css files
which are checked for existance and placed linkded to the generated page.
John Rankin wrote:
> Thanks, Bernhard.
> I ended up doing the following:
> - combine the PrintablePage and Publish scripts to use a print.css
> - check if file exists $group.css and append a link to $group.css
> I'm still thinking about $action.css as I use the same styles to give
> a uniform look to search, edit and history pages.
> John Rankin wrote:
>> Yup. To be more precise, here's the relevant section from a Group.php
>> of mine, where the "-it" suffix stands for "italian":
>> ---------------------------- snip
>> --------------------------------------- ### BEGIN grop-specific
>> customization; this section must come last. ## See
>> ## Include various (localized) add-on packages.
>> # Conditional inclusion of flexlayout.php
>> # See http://www.pmichaud.com/wiki/Cookbook/FlexLayout
>> # The local.css file should be customized as desired.
>> Is there a requirement for scripts/pgcust.php to add a reference to
>> Group.css as well as including Group.php?
>> Then one could do per-group styling by exception to the pmwiki.css
>> and local.css -- this would make it a lot easier to set a site
>> then apply per-group 'skins'
>> Indeed, one could even allow visitors to choose their own skins,
>> A Group.css template could define 3-5 classes which would change the
>> whole group look, while keeping a consistent underlying framework.
>> By extension, would could even do Page.css if needed...
>> One can do this in the Group.php file, but css is probably a better
>> Pmwiki-users mailing list
>> Pmwiki-users at pmichaud.com
> Pmwiki-users mailing list
> Pmwiki-users at pmichaud.com
More information about the pmwiki-users