On Thu, 03 Feb 2011 13:52:30 -0800, Brion Vibber wrote:
On Thu, Feb 3, 2011 at 1:19 PM, Dan Nessett dnessett@yahoo.com wrote:
Our site has 4 skins that display the logo - 3 standard and 1 site- specific. The site-specific skin uses rounded edges for the individual page area frames, while the standard skins use square edges. This means a logo with square edges looks fine for the standard skins, but not for the site-specific skin. A logo with rounded edges has the opposite characteristic.
The programmer who designed the site-specific skin solved this problem with a hack. The absolute url to a different logo with rounded edges is hardwired into the skin code. Therefore, if we want to reorganize where we keep the site logos (which we have done once already), we have to modify the site-specific skin code.
While it is possible that no one else has this problem, I would imagine there are skins out there that would look better if they were able to use a skin specific logo (e.g., using a different color scheme or a different font).
My question is: has this issue been addressed before? If so, and there is a good solution, I would appreciate hearing of it.
A couple ideas off the top of my head:
- You could use CSS to apply rounded corners with border-radius and its
-vendor-* variants. (May not work on all browsers, but requires no upkeep other than double-checking that the rounded variant still looks good. Doesn't help with related issues like an alternate color scheme for the logo in different skins.)
- Your custom skin could use a custom configuration variable, say
$wgAwesomeSkinLogo. Have it use this instead of the default logo, and make sure both settings get updated together. * You could use a fixed alternate path which can be determined by modifying the string in $wgLogo. Be sure to always store and update the second logo image correctly.
- You could create a script that applies rounded corners or changes
colors in an existing image file and saves a new one, then find some way to help automate your process of creating alternate logo images in the above.
-- brion
Thanks. I think the second idea works best for us. It also suggests the use of a global $wgSkinLogos that points to a directory where all of the skin logos are kept. Any reason why this is a bad idea?