DEPRECATION WARNING

This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.

Skin 360¶

Author:	Kasper Skårhøj
Created:	2002-11-01T00:32:00
Changed by:	Kasper Skårhøj
Changed:	2003-12-27T21:26:25
Author:	Kasper Skårhøj
Email:	kasper@typo3.com
Info 3:
Info 4:

Skin 360¶

Extension Key: skin360

This document is published under the Open Content License

available from http://www.opencontent.org/opl.shtml

The content of this document is related to TYPO3

- a GNU/GPL CMS/Framework available from www.typo3.com

Table of Contents¶

EXT: My Extension 1

Introduction 1

What does it do? 1

Screenshots 1

Users manual 1

FAQ 1

Adminstration 1

FAQ 2

Configuration 2

FAQ 2

Reference 2

Tutorial 2

Known problems 2

To-Do list 2

Changelog 2

Introduction¶

What does it do?¶

It tests and demonstrates the skinning API of TYPO3 ver. 3.6.0. It uses PNG files with alphachannel transparency and therefore it works best in Mozilla and Opera browsers while Internet Explorer cannot render the transparency correctly which results in an undesirabel effect.

The intension of this skin is to inspire graphical designers to create an array of professional skins for TYPO3. It is meant as proof-of- concept.

Screenshots¶

The login screen of the skin. The image to the left is rotating between a list of images in a folder.

The backend of skin with all icons substituted with PNG alternatives (taken from the KDE skin “slick”) in other sizes than the default icons:

IMPORTANT: Skinning and copyrights¶

Notice that rebranding TYPO3 is illegal (by default copyright and trademark laws, see details here ). Rebranding means that you give the TYPO3 cms another name, presumably to sell “your product” to a customer. So never try to brand TYPO3 as if it was your own product to which you have the copyright.

But how far can you go then? Well, with skinning you can actually change all graphics of the application, including the login screen logo and logo in the top left corner of the backend. As long as these logos does not convey the idea that the CMS is something else than TYPO3 you can personalize these logos as much as you like. You can name them after the company to which you sell the solution so it feels personal for them. Or you could mix TYPO3s logo with your companys logo, stating something like “My Company proudly uses TYPO3 blablabla” or whatever.

The main reason why you can change these logos is that the official TYPO3 logo and name is included in the copyright notice of the login screen and “About Modules” screen. This notice must never be changed by you and must display as is. This is what ultimately identifies to the user that the underlying CMS is in fact TYPO3, not something else.

On this screenshot you can see it in effect: The top logo (#1) could be the one of your company or customer, adding a personal touch to the login screen. In the bottom (#2) you will see the TYPO3 logo and product name in the copyright notice. This must not be changed.

Notice, that the bottom message (#2) is not something we have made up ourselves but required by the GPL license according to this part of the license:

...
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) year name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.
...

(The GPL license can be found in the file “GPL.txt” inside the TYPO3 source code)

Skin 360 - 3