[Pmwiki-users] printable-page, flexlayout, and webmenu

Sun Aug 24 17:14:01 CDT 2003

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. 

JR
-- 

On Wednesday, 20 August 2003 4:59 PM, bernhard at weichel21.de wrote:

This can easily be done in flexlayout.php.

$HTMLStartFmt = "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01
Transitional//EN\"
    \"http://www.w3.org/TR/html40/loose.dtd\"><html><head>
  <link rel='stylesheet' href='\$ScriptDir/pmwiki.css' type='text/css' />
  <link rel='stylesheet' href='\$ScriptDir/local/local.css' type='text/css'
/>
  <link rel='stylesheet' href='\$ScriptDir/local/\$action.css'
type='text/css' />
  <link rel='stylesheet' href='\$ScriptDir/local/\$style.css'
type='text/css' />
  <link rel='stylesheet' href='\$ScriptDir/local/\$action_$style.css'
type='text/css' />";

I run it with this adjustment. But it would be better if I check if the
files
really exist. Currently I am flooding my webserver log ;-)

bernhard.

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
> http://www.pmichaud.com/wiki/PmWiki/PerGroupCustomizations
>
> ## 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 layout,
> then apply per-group 'skins'
>
> Indeed, one could even allow visitors to choose their own skins,
> maybe.
>
> 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
> approach.
>
> JR
>
>
>
> _______________________________________________
> Pmwiki-users mailing list
> Pmwiki-users at pmichaud.com
> http://pmichaud.com/mailman/listinfo/pmwiki-users_pmichaud.com