But why create a new system to learn? What is the advantage of doing this instead of just using the tried and tested extensions directory? What stops a new user from plopping the folder into the extensions directory by accident out of habit?
On Wed, May 21, 2014 at 5:42 PM, Daniel Friesen daniel@nadir-seen-fire.com wrote:
On 2014-05-21, 6:02 AM, Jon Robson wrote:
I've always found it silly that skins are installed in a different way to extensions. It seems silly to teach a user 2 ways. To be honest I still haven't got the hang of skin installation. I usually crudely plop a folder in the skins directory which I'm pretty sure is wrong.
Thus, I would personally make skins installable in the same way.
If there is a need to manage that process better, I would steer someone in the direction of writing a SkinInstaller extension. Such an extension could protect the end user from the installation process and could also provide lots of MediaWiki coolness such as reviewing skins, updating skins and publishing skins.
This would be my vision to steer towards any how...
The current process for installing an extension is:
- Plop a folder in the extensions directory.
- Put require_once( "$IP/extensions/{name}/{name}.php" ); where {name} is the name of that folder you just plopped in.
The process I'm suggesting for skins is:
- Plop a folder in the skins directory.
- Put require_once( "$IP/skins/{name}/{name}.php" ); where {name} is the name of that folder you just plopped in, which is also the name you will use in &useskin= or $wgDefaultSkin.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l