> You could ignore the default logo and hard code an alternative into
> the skin, like this image that the old skin used:
> http://wiki.services.openoffice.org/OOoWiki_Logo_06.png
> or make it more OOo-esque with a blue background, e.g.
> http://www.patentpending.co.nz/images/openoffice/siteconcept-monobook.png
I like the concept.
The global default logo is set in the LocalSettings.php file with the
$wgLogo variable (small change needed in the config to get that working
right... tested on MonoBook). It is used where a logo is not explicitly
used in a skin.
> But the more important issue is probably updating the skin with code
> for new plugins - e.g.
>
> <?php
> if(isset($GLOBALS['wgSpecialPages']['Collection'])) {
> Collection::printPortlet();
> }
> ?>
Right... ummm.. we can use that as an incentive to use the OooWiki skin
though :-)
I have added it to the Monobook skin. Do we need to do it to any other
skins?
C.
--
Clayton Cornell [email protected]
OpenOffice.org Documentation Project co-lead
StarOffice - Sun Microsystems, Inc. - Hamburg, Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
