On Wed, Jul 29, 2009 at 9:01 AM, Clayton<[email protected]> wrote:
> The OOoWiki skin needs to be updated now that we are on the current
> version of MedaiWiki.

I can help you take a look at it and see what has changed.

> The OOoWiki skin is based on the MonoBook skin, following the basic
> instructions here:
> http://www.mediawiki.org/wiki/Manual:Skins/From_Meta
> The OOoWiki skin as you see it now is based on an old MonoBook, and is
> missing a lot of the updates and changes that went into the MonoBook

I can lend some help since I did the original port I would need to
read up the link you send me and do some diff on the original CSS.

> skin since MedaiWiki 1.11.0 (the version we based the OOoSkin on)  Some
> of those changes and updates are limiting the functionality of new or
> updated extensions we use on the Wiki.
>
> So I've attempted to "start again" with a new copy of the MonoBook skin
> php file.  I've adjusted the bits (plus some new ones) to point at the
> oooskin directory instead of the monobook directory - this is where it
> is supposed to pick up on the main.css, images etc.  On loading that new
> skin.. I get the Monobook skin.  If I check the page source I see:
>
>   var skin = "monobook";
>
> in the headers instead of:
>
>     var skin = "oooskin";
>
> which you can see when you load the old skin.
>
> So... I've missed something somewhere.  Anyone want to take a look at
> this with me?  I can send the php file off list.

Sure I can help out.

> 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]
>
>



-- 
Alexandro Colorado
OpenOffice.org Espa&ntilde;ol
IM: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to