• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

In Item1321 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 had before.

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."

-- PTh

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

CC

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.

-- PTh

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.

CC

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 oopsattention.classic.tmpl can be removed (after a careful merge) so that it falls back to the default template.

-- PTh

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).

CC

Agreed not to document default templates as a skin at http://twiki.org/cgi-bin/view/Codev/DakarReleaseMeeting2006x01x16. Closed.

CC

ItemTemplate
Summary Create new DefaultSkin
ReportedBy PeterThoeny
Codebase

SVN Range Tue, 03 Jan 2006 build 8080
AppliesTo Engine
Component

Priority Urgent
CurrentState Closed
WaitingFor

Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r9 - 2006-01-16 - CrawfordCurrie
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback