I have learned that the ClassicSkin
was promoted from a pseudo skin to a real skin. This is fair enough.
But: The look of the default templates is not accessible and not documented. We therefore need a new DefaultSkin
that steps into the role the ClassicSkin
Part of description: "This is not really a skin. It is the set of default templates, shown if no skin is activated, or if a name of a non-existing skin is specified. The default templates are part of every TWiki distribution."
Peter now understands the difference between default templates and a skin, and agreed to do nothing in http://twiki.org/cgi-bin/view/Codev/DakarReleaseMeeting2006x01x07
Funny endorsment, "Peter now understands the difference between default templates and a skin". I thought it was me who designed the template and skins in the first place.
CORRECTION: I never said that I agree. I did not even say that I disagree and commit. The outcome of that discussion was "no consensus reached, lets move on". Please do not distort the facts.
Sorry, Peter, I didn't think I was
"distorting the facts". I understood from our call that you regarded the default templates to constitute a "skin", and we discussed at length why I (and others) felt it was not appropriate to call it a skin. Hence my remark "Peter now understands....". I meant "Peter now understands why CC
doesn't want to call the default templates a skin". I didn't have access to the meeting script when I remarked here, but I had been left with the strong impression that you had understood the logic of the majority opinion, and would not generate a DefaultSkin
topic (which I now see from re-reading the script is not the case). Which means we have to have the discussion all over again, which is a shame.
I noticed that the skin and default templates are already totally out of snyc. Is anyone volunteering to compare them and merge them back? Some files such as
can be removed (after a careful merge) so that it falls back to the default template.
Sure they are out of synch; we split them specifically so they could
get out of synch.
There is a major problem sharing the messages between skins. See Item1401
If I were you, I'd be very, very
cautious about allowing ClassicSkin
to fall back to the default templates for anything other than messages. As stated before, the default templates are going to change extensively
soon, and if you already have a template in a skin that provides a specific look and feel, I'd hang on to it (that's why I moved ClassicSkin
to a contrib in the first place; in order to protect it).
Agreed not to document default templates as a skin at