On 2014-05-20, 3:48 PM, Isarra Yos wrote:
Out of curiosity, what are your reasons for advocating
names over the standard camelcase format used throughout the rest of
I included those in my bullet points.
* The skinname you require is the same one assigned to $wgValidSkins
and set on $wgDefaultSkin and set on $skinname, and $stylepath.
* For all skins using the old autoload pattern the assets directory
remains them same, so nothing has to be re-cached.
There's also a third reason.
There are 3 names for a skin containing two words:
* Foo Bar
Foo Bar is exposed to users in the interface as the human readable name.
And foobar is exposed in &useskin= $wgDefaultSkin and the current
directory asset structure, in essence it IS the canonical name of the skin.
FooBar however generally isn't exposed anywhere. It exists exclusively
for things like skin class names like SkinFooBar and optionally some
filenames, both of which are internal to the skin.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/