Wiki source code of Skins

Version 18.2 by Sorin Burjan on 2011/04/13

Show last authors
1 (% class="floatinginfobox" %)
2 (((
3 **Contents**
4
5 {{toc depth="3" start="2"/}}
6 )))
7
8 = XWiki Skins =
9
10 == How to create a new Skin ==
11
12 {{warning}}
13 To create a new Skin, you must have access to the server side of the XWiki Enterprise instance.
14 {{/warning}}
15
16 To create a new Skin, you have to create a new direcory inside the webapps/xwiki/skins folder and then add Velocity templates,CSS stylesheets, Javascript files and images inside it. For example, if you want to remove the logo from the header of the pages, follow these steps:
17
18 1. Inside the webapps/xwiki/skins folder, create a folder named myskin. Copy all files from webapps/xwiki/skins/colibri folder into your new skin directory.
19 1. Change the Skin at global or instance level and set it as myskin ( see [[this>>AdminGuide.Skins]] page for more informations about how to change the Skin )
20 1. Open any page in view mode and you will notice that myskin layout is the same as the colibri layout (if the skin changes to albatross means that your theme wasn't used. Check the names of your skin directory. Note that skin names are case-sensitive)
21 1. Change the global template:
22 1*. to remove the logo, modify the global.vm template under the new Skin and delete the line:(((
23 {{code language="html"}}
24 <img src="$!logourl" alt="Wiki Logo"/>
25 {{/code}}
26 )))
27 1. Save the template
28
29 Open any page in view mode and you will notice that the XWiki logo is not displayed anymore. Congratulations! You have created a new minimal XWiki Skin.
30
31 == How to override a Skin ==
32
33 {{warning}}
34 To change the Skin, the user must have administrating rights. In the case that you have these rights, make sure that you switch to the Advanced mode in your profile, to enable the advanced options on the top main menu.
35 {{/warning}}
36
37 An alternative for creating a new Skin is the possibility to override an existing Skin. The advantage of overriding an existing Skin is the fact that you don't need access to the server filesystem in order to modify the files used by the current Skin.
38 To override a Skin, you have to use the same document that is used to store the Skin.
39 {{id name="5a"/}}
40
41 === A. Creating a Skin document ===
42
43 {{warning}}
44 You need to have the **advanced edit mode** activated to access the object editor. Please refer to [[platform:Features.PageEditing]] for more information.
45 {{/warning}}
46
47 To create a new Skin document, follow these steps:
48
49 1. Create a new page. Name it MySkinPage(((
50 [[image:createSkinPage.png||style="border:1px solid black; width:650px"]]
51 )))
52 1. Edit the document's objects (Edit -> Objects)
53 1. Add an object of type XWiki.XWikiSkins to the document
54 1. Click on add
55 1. Set the base skin property to colibri. Now, you use colibri as a base skin. As you can see, no files were copied on the file system, but your skin uses colibri.(((
56 [[image:addSkinObject.png||style="border:1px solid black; width:650px"]]
57 )))
58 1. Save the document
59
60 === B. Working with the XWiki.XWikiSkins class ===
61
62 The base element in overriding a Skin is the XWiki.XWikiSkins class ( http://localhost:8080/xwiki/bin/view/XWiki/XWikiSkins ). In order to modify the templates or the files used by a Skin, you have to work with the properties of this class. By default, the Skin class contains a set of properties that allows you to override some of the templates and files used by the Skin, and it also allows you to set the name of the logo displayed in the header of the interface.
63 To override other templates or files, you have to add new properties to the Skin class. For example, if you want to override myfile.vm ( or myfile.css, or myfile.js ), follow these steps:
64
65
66 1. Go to the XWiki.XWikiSkins document
67 1. Edit the document's class (Edit -> Class) or follow this link: http://localhost:8080/xwiki/bin/edit/XWiki/XWikiSkins?editor=class
68 1. Add a new property myfile.vm as TextArea type
69 1. Click on Add. The myfile.vm property should appear in the list(((
70 [[image:editXWikiSkins.png||style="border:1px solid black; width:650px"]]
71 )))
72 1. Save the document
73
74 === C. Using a Skin document ===
75
76 To use a Skin document, follow these steps:
77
78 1. Go to the (% class="sectionblockcodecolored" %)Skin(%%) property from inside the (% class="sectionblockcodecolored" %)Administration(%%) page, Presentation section
79 1. Set the value of the files as being the full name of the Skin document. For our skin page created above, we will type Main.MySkinPage
80 1. Save the preferences
81
82 === D. Overriding the Skin components ===
83
84 Let's add a "HELLO," before the username on the top right menu, not by modifying the (% class="sectionblockcodecolored" %)menuview.vm(%%) template on the server, but overriding it inside the Skin document. Follow these steps:
85
86 ==== Method 1: By editing the XWiki.XWikiSkins properties on the Skin document ====
87
88
89 1. Add a TextArea property named menuview.vm to the XWiki.XWikiSkins class
90 1. Edit your skin document's objects (Edit -> Objects) and open the properties of the object
91 1. Copy the original content of the menuview.vm template and paste it in the property field named menuview.vm. If you don't have access to the server filesystem, open the template by following http://localhost:8080/xwiki/templates/global/vmmenuview.vm
92 1. (((
93 Replace the following code:
94 {{code language="html"}}
95 #xwikitopmenuentrystart($xwiki.getURL($xcontext.user, 'view') "$msg.get('core.menu.type.profile')__SEPARATOR__$!xwiki.getUserName($xcontext.user, false)" 'tmUser' 'hasIcon')
96 {{/code}}
97 )))
98 (((
99 with({{code language="html"}}
100 #xwikitopmenuentrystart($xwiki.getURL($xcontext.user, 'view') "$msg.get('Hello')__SEPARATOR__$!xwiki.getUserName($xcontext.user, false)" 'tmUser' 'hasIcon')
101 {{/code}}
102 )))
103 1. Save the document
104 )))
105
106 ==== Method 2: By attaching files to the current Skin document ====
107
108 1. create a copy of the global.vm template; if you don't have access to the server filesystem, open the template by following one of these links:
109 1*. http://localhost:8080/xwiki/skins/mybaseskin/global.vm ( where mybaseskin is the current Skin used in the Skin document ), or
110 1*. if the previous link is not valid, go to http://localhost:8080/xwiki/templates/global.vm
111 1. replace the following code inside the copy of global.vm template:(((
112 {{code language="xml"}}
113 <a class="glink"
114 href="$!xwiki.getURL($context.user, 'view')"
115 id="headeruser">
116 $!xwiki.getUserName($context.user, false)
117 </a>
118 {{/code}}
119 )))with(((
120 {{code language="xml"}}
121 <a class="glink"
122 href="$!xwiki.getURL($context.user, 'view')"
123 id="headeruser">
124 HELLO,
125 $!xwiki.getUserName($context.user, false)
126 </a>
127 {{/code}}
128 )))
129 1. attach the copy of global.vm template to the current Skin document page
130
131 Now, open any document in view mode and you will notice the nice "HELLO," before your username.
132 Follow the same process in order to override (% class="sectionblockcodecolored" %)Javascript(%%) and (% class="sectionblockcodecolored" %){{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}}(%%) files ( http://localhost:8080/xwiki/skins/colibri/myfile.css ).
133
134 ==== 3. Overriding a skin resource ====
135
136 Just like templates, resource files such as images or css/js files can be overridden. To do that, the replacement must be attached to the Skin document, making sure it complies with the naming convention explained below. To find out the right name for your replacement resource, here is the trick:
137
138 1. find the path on the filesystem of the resource to replace (you can easily obtain that information using development tools such as [[Firebug>>http://getfirebug.com/]]); for instance, let's say this path is either
139 {{code}}/xwiki/resources/icons/silk/myicon.gif{{/code}}
140 for a resource found in the general resource directry, or
141 {{code}}/xwiki/skins/colibri/myimage.png{{/code}}
142 if the resource is specific to a certain skin, in this case 'colibri'.
143 1. strip from this path everything from the beginning until 'resources/' or the name of the skin, included; in the previous examples, you will obtain in the first case
144 {{code}}icons/silk/myicon.gif{{/code}}
145 and in the second case simply
146 {{code}}myimage.png{{/code}}
147 1. in this path, replace '/' with '.'; after this operation, we will get {{code}}icons.silk.myicon.gif{{/code}} for the first image example, while the second one remains unchanged. **This is the name of the file corresponding to the resource that you need to attach to the Skin document in order to make the replacement**.
148 1. create a file named as explained above and attach it to your Skin
149
150 {{info}}
151 **Technical note**: This trick works for any resource whose URL is generated in the skin by the {{code}}$xwiki.getSkinFile(){{/code}}, {{code}}$xwiki.jsfx(){{/code}} or {{code}}$xwiki.ssfx(){{/code}} methods, for instance like this:
152
153 {{code language="none"}}
154 .infomessage {
155 background-image: url("$xwiki.getSkinFile('icons/silk/information.gif')");
156 }
157 {{/code}}
158
159 In this case, {{code}}$xwiki.getSkinFile('icons/silk/information.gif'){{/code}} will first search for an image called 'icons.silk.information.gif' attached to the configured Skin document, if any. If that image exists, it will generate its URL. Otherwise, it will continue to search for 'icons/silk/information.gif' in the base skins and finally in the general 'resources/' directory.
160 {{/info}}
161
162 {{id name="5e"/}}
163
164
165 === E. Adding new components to the Skin ===
166
167 If you want to add new files to the skin, like (% class="sectionblockcodecolored" %){{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} (%%) or (% class="sectionblockcodecolored" %)Javascript(%%) files, you have two options:
168
169 * attach the files to the Skin document and reffer them by their URL, or
170 * add new properties to the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) object from inside the Skin document, and refer them by their name
171
172 For example, if you want to add a new {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} file to the Skin, named (% class="sectionblockcodecolored" %)mynewfile.css(%%), follow one of these set of steps:
173
174 |(% style="width: 60%; color: rgb(34, 34, 34);" %)(((
175 1. attach the {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} file to the Skin document
176 1. override the stylesheets.vm template ( check the section [[D>>#5d]] to learn how to override a Skin component ), and add the reference to your file in the template:(((
177 {{code language="xml"}}
178 <link rel="stylesheet"
179 type="text/css"
180 href="$xwiki.getSkinFile('mynewfile.css')"
181 />
182 {{/code}}
183 )))
184 1. save the document
185 )))|(((
186 [[[[image:7.png||style="border: 3px solid rgb(221, 221, 221);" width="100%"]]>>attach:7.png]]
187 )))
188
189 OR
190
191 |(% style="width: 60%; color: rgb(34, 34, 34);" %)(((
192 1. add a new property to the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%), name it (% class="sectionblockcodecolored" %)mynewfile.css(%%) ( check the section [[B>>#5b]] for more information about how to work with this class ), edit the Skin document's objects ( use the top-left menu: (% class="sectionblockcodecolored" %)EDIT -> OBJECTS(%%) ), and paste the {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} code into the (% class="sectionblockcodecolored" %)mynewfile.css(%%) field
193 1. override the (% class="sectionblockcodecolored" %)style.css(%%) component ( see the section [[D>>#5d]] for more information about how to override a Skin compoment ) and add the following line to the content of the (% class="sectionblockcodecolored" %)style.css(%%) property:(((
194 {{code language="css"}}
195 @import "mynewfile.css";
196 {{/code}}
197 )))the important thing is to add a reference to the new component from a existing one; you must know most of the components content, so that you will take the best decision about which existing component will contain a reference to the new one
198 1. save the document
199 )))|(((
200 [[[[image:8.png||style="border: 3px solid rgb(221, 221, 221);" width="100%"]]>>attach:8.png]]
201 )))
202
203 Open any document in view mode and you will notice that the stylesheet is now applied.
204
205 {{id name="5f"/}}
206
207 === F. Using (% class="sectionblockcodecolored" %)images(%%) in a Skin document ===
208
209 {{id name="5f1"/}}
210
211 ==== 1. Changing the (% class="sectionblockcodecolored" %)logo(%%) ====
212
213 For example, if you want to add an image named (% class="sectionblockcodecolored" %)myimage.jpg(%%) as being the logo for the current Skin, follow these steps:
214
215 1. attach the image to the Skin document
216 1. edit the document's objects ( use the top-left menu: (% class="sectionblockcodecolored" %)EDIT -> OBJECTS(%%) )
217 1. use the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) object and set the (% class="sectionblockcodecolored" %)Logo(%%) property as being the name of the attached image: (% class="sectionblockcodecolored" %)myimage.jpg
218 1. save the document
219
220 Open any page in view mode and you will notice that the logo is now changed.
221
222 {{id name="5f2"/}}
223
224 ==== 2. Adding images to the Skin interface ====
225
226 To add images to the interface, attach them to the Skin document and use them in the {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} code. For example, if you want to use (% class="sectionblockcodecolored" %)myimage.jpg(%%) as background image for the pages inside your XWiki Enterprise instance, follow these steps:
227
228 1. attach the image to the Skin document
229 1. choose one of these actions:
230 1*. add a new {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} component to the Skin, name it (% class="sectionblockcodecolored" %)pagebackground.css(%%) and add a reference to it from the (% class="sectionblockcodecolored" %)style.css(%%) component ( see the section [[E>>#5e]] for more information about how to add new components to the Skin )
231 1*. override the (% class="sectionblockcodecolored" %)mybaseskin.css(%%) component ( where mybaseskin is the name of the current Skin - for example: (% class="sectionblockcodecolored" %)albatross.css(%%), (% class="sectionblockcodecolored" %)toucan.css(%%) or (% class="sectionblockcodecolored" %)colibri.css(%%) )
232 1. paste the following code inside the {{html}}<acronym title="Cascading Style Sheets">CSS</acronym>{{/html}} component:(((
233 {{code language="css"}}
234 body{
235 background-image: url($xwiki.getSkinFile("myimage.jpg"));
236 }
237 {{/code}}
238 )))
239
240 Open any page in view mode and you will notice that the the background of the page contains your image.
241 Have fun taking advantage of the power of XWiki Skins!
242
243 == More about XWiki Skins ==
244
245 In order to find more about XWiki Skins, check the [[Skins Tutorial>>AdminGuide.Skins]] from inside the Admin Guide and the [[Skins Tutorial>>Features.Skins]] from inside the User Guide
246
247 == Further reading ==
248
249 * the [[XWiki Data Model>>http://platform.xwiki.org/xwiki/bin/view/DevGuide/DataModel]]
250 * using the [[Skin Editor Application>>extensions:Extension.Skin Editor Application]]
251 * [[edit only one object>>http://dev.xwiki.org/xwiki/bin/view/Drafts/EditOneObject]]

Get Connected