Test case:

• In Pattern skin, select different language
• Add ?skin=classic to URL
• All system links are in English

-- PTh

---

Changed priority to low.

AC

This might look like low, but:

• Admins can customize the Pattern skin, but more often then not, they create their own skin based on the simple classic skin. A TWiki look consistent with the intranet is important to get TWiki accepted within an organization.
• TWiki do not leave a good impression on quality if we ship a product where a skin is half backed.

-- PTh

---

This is all understood. This item is not discarded. Low priority means that other bug fixes need more attention. Unless the "normal priority" is a 'note to self' in which case I suggest you try to get SVN access. AC

---

Also, i'm starting to think that having even 2 skins in the release is a mistake, as the classic skin is suffering from neglect (as you have noticed Peter), and without anyone actually willing to do the work, its only going to fall further behind - perhaps its better to simply focus on making one skin to rule them all ?

-- SD

We are making assumptions about the usage of skins. I suggest we poll the community to see who cannot use Pattern skin. If there is anyone of note ask them to maintain it. Classic skin is not useful to me.

-- MC

moved to enhancement queue - if someone wants to do the work, we'd welcome it -- SD

---

Personally I think having a couple of skins in the release is a good idea, but I'm not convinced we have the right skins. The classic skin is just not simple enough, and is architecturally difficult to use as a basis for deriving new skins.

Further discussion moved to TWiki:Codev.StandardSkins, and deferred this item to Edinburgh. CC

Undeferred, post Dakar CC

---

Classic skin is no longer shipped.

-- ArthurClemens - 25 Jan 2009