>> What kind of decoupling did you have in mind?
>
> Not specifying that each skin has to have exactly one lc identifier
> and then starting to rely on this requirement and generate all sorts
> of secondary names, identifiers, paths, class names, etc. from that.
> E.g why not just ask that skin for
On 1 June 2014 22:45, Daniel Friesen wrote:
> What kind of decoupling did you have in mind?
Not specifying that each skin has to have exactly one lc identifier
and then starting to rely on this requirement and generate all sorts
of secondary names, identifiers, paths, class names, etc. from that.
On 2014-06-01, 3:25 AM, Stephan Gambke wrote:
> I'll not answer all your points. I'd just like to (again) question the
> need to keep all the names and identifiers of a skin identical
> whatever the cost. Maybe I am daft, everybody else seems to take this
> as some given great goal and nobody else
To unsubscribe go here:
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 6/1/14, Sajjad Manal wrote:
> Hey.
> May I please know how to unsubscribe from the mails from Wikimedia??
> On 1 Jun 2014 13:14, "Daniel Friesen" wrote:
>
>> I'm not happy at all with how the skin naming topic "en
Hey.
May I please know how to unsubscribe from the mails from Wikimedia??
On 1 Jun 2014 13:14, "Daniel Friesen" wrote:
> I'm not happy at all with how the skin naming topic "ended".
>
> Throughout the discussion I explained a variety of reasons why switching
> to a CamelCased structure and skin n
I'll not answer all your points. I'd just like to (again) question the
need to keep all the names and identifiers of a skin identical
whatever the cost. Maybe I am daft, everybody else seems to take this
as some given great goal and nobody else is questioning it.
As I see it it introduces all kinds
Some ideas I AM currently in favour of:
* Deprecate and drop the autoloader.
* Split the classes in skin files into separate class files.
* Move skins out of core (but I still believe our lower case skin
directory names should remain lower case)
* Make the user facing &useskin=, etc...
I'm not happy at all with how the skin naming topic "ended".
Throughout the discussion I explained a variety of reasons why switching
to a CamelCased structure and skin name was a bad idea. We discussed
them, some like the caching issue got valid comments back on why they're
not issues, others rem
