Wiki source code of Skins
Version 24.1 by Guillaume Delhumeau on 2015/03/11
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | * 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 | * 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 | * 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 | * Change the global template:to remove the logo, modify the global.vm template under the new Skin and delete the line:((( | ||
| 22 | {{code language="html"}} | ||
| 23 | <img src="$!logourl" alt="Wiki Logo"/> | ||
| 24 | {{/code}} | ||
| 25 | ))) | ||
| 26 | * Save the template | ||
| 27 | |||
| 28 | 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. | ||
| 29 | |||
| 30 | == How to override a Skin == | ||
| 31 | |||
| 32 | {{warning}} | ||
| 33 | 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. | ||
| 34 | {{/warning}} | ||
| 35 | |||
| 36 | 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. | ||
| 37 | To override a Skin, you have to use the same document that is used to store the Skin.\\ | ||
| 38 | |||
| 39 | === A. Creating a Skin document === | ||
| 40 | |||
| 41 | {{warning}} | ||
| 42 | You need to have the **advanced edit mode** activated to access the object editor. Please refer to [[platform:Features.PageEditing]] for more information. | ||
| 43 | {{/warning}} | ||
| 44 | |||
| 45 | To create a new Skin document, follow these steps: | ||
| 46 | |||
| 47 | * Create a new page. Name it MySkinPage((( | ||
| 48 | [[image:createSkinPage.png||style="border: 1px solid black; width: 650px;"]] | ||
| 49 | ))) | ||
| 50 | * Edit the document's objects (Edit -> Objects) | ||
| 51 | * Add an object of type XWiki.XWikiSkins to the document | ||
| 52 | * Click on add | ||
| 53 | * Set the base skin property. The base skin property points to the skin you wish to override. You can use either the filesystem skin directory name (for a filesystem skin to override) or the page name where the skin is defined (for overriding a page-based skin). Set it to ##colibri## for using the ##colibri## skin as a base skin. As you can see, no files were copied on the file system, but your skin uses colibri.((( | ||
| 54 | [[image:addSkinObject.png||style="border: 1px solid black; width: 650px;"]] | ||
| 55 | ))) | ||
| 56 | * Save the document | ||
| 57 | |||
| 58 | === B. Working with the XWiki.XWikiSkins class === | ||
| 59 | |||
| 60 | {{warning}} | ||
| 61 | Since 7.0RC1, this mechanism is deprecated. You don't need to edit the XWiki.XWikiSkins class anymore. You should simply use the [[extensions:Extension.Skin Application]]). | ||
| 62 | {{/warning}} | ||
| 63 | |||
| 64 | 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. | ||
| 65 | 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: | ||
| 66 | |||
| 67 | |||
| 68 | * Go to the XWiki.XWikiSkins document | ||
| 69 | * Edit the document's class (Edit -> Class) or follow this link: http:~/~/localhost:8080/xwiki/bin/edit/XWiki/XWikiSkins?editor=class | ||
| 70 | * Add a new property myfile.vm as TextArea type | ||
| 71 | * Click on Add. The myfile.vm property should appear in the list((( | ||
| 72 | [[image:editXWikiSkins.png||style="border: 1px solid black; width: 650px;"]] | ||
| 73 | ))) | ||
| 74 | * Save the document | ||
| 75 | |||
| 76 | === C. Using a Skin document === | ||
| 77 | |||
| 78 | To use a Skin document, follow these steps: | ||
| 79 | |||
| 80 | * Go to the skin property from inside the Administrationpage, Presentation section | ||
| 81 | * 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 | ||
| 82 | * Save the preferences | ||
| 83 | |||
| 84 | === D. Overriding the Skin components === | ||
| 85 | |||
| 86 | Let's add a "Hello" before the username on the top right menu, not by modifying the menuview.vm template on the server, but overriding it inside the Skin document. Follow these steps: | ||
| 87 | |||
| 88 | ==== Method 1: By editing the XWiki.XWikiSkins properties on the Skin document ==== | ||
| 89 | |||
| 90 | {{warning}} | ||
| 91 | Since 7.0RC1, this method is deprecated. You don't need to edit the XWiki.XWikiSkins class anymore. You should simply use the [[extensions:Extension.Skin Application]]). | ||
| 92 | {{/warning}} | ||
| 93 | |||
| 94 | * Add a TextArea property named menuview.vm to the XWiki.XWikiSkins class((( | ||
| 95 | [[image:XWikiSkinsMenuView.png||style="border: 1px solid black; width: 650px;"]] | ||
| 96 | ))) | ||
| 97 | * Edit your skin document's objects (Edit -> Objects) and open the properties of the object | ||
| 98 | * 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/menuview.vm (to access a template from the skin, use http:~/~/localhost:8080/xwiki/skins/colibri/) | ||
| 99 | * Replace the following code:((( | ||
| 100 | {{code language="html"}} | ||
| 101 | #xwikitopmenuentrystart($xwiki.getURL($xcontext.user, 'view') "$msg.get('core.menu.type.profile')__SEPARATOR__$!xwiki.getUserName($xcontext.user, false)" 'tmUser' 'hasIcon') | ||
| 102 | {{/code}} | ||
| 103 | |||
| 104 | with | ||
| 105 | |||
| 106 | {{code language="html"}} #xwikitopmenuentrystart($xwiki.getURL($xcontext.user, 'view') "$msg.get('Hello')__SEPARATOR__$!xwiki.getUserName($xcontext.user, false)" 'tmUser' 'hasIcon'){{/code}} | ||
| 107 | [[image:MySkinPageWithMenuView.png||style="border: 1px solid black; width: 650px;"]] | ||
| 108 | ))) | ||
| 109 | * Save the document | ||
| 110 | |||
| 111 | ==== Method 2: By attaching files to the current Skin document ==== | ||
| 112 | |||
| 113 | * Create a file on your computer called menuview.vm. Copy the original content of the menuview.vm into your local file. If you don't have access to the server filesystem, open the template by following http:~/~/localhost:8080/xwiki/skins/colibri/menuview.vm | ||
| 114 | * Replace the following code:((( | ||
| 115 | {{code language="html"}} | ||
| 116 | #xwikitopmenuentrystart($xwiki.getURL($xcontext.user, 'view') "$msg.get('core.menu.type.profile')__SEPARATOR__$!xwiki.getUserName($xcontext.user, false)" 'tmUser' 'hasIcon') | ||
| 117 | {{/code}} | ||
| 118 | |||
| 119 | with | ||
| 120 | |||
| 121 | {{code language="html"}} | ||
| 122 | #xwikitopmenuentrystart($xwiki.getURL($xcontext.user, 'view') "$msg.get('Hello')__SEPARATOR__$!xwiki.getUserName($xcontext.user, false)" 'tmUser' 'hasIcon') | ||
| 123 | {{/code}} | ||
| 124 | ))) | ||
| 125 | * Attach the copy of menuview.vm template to the current Skin document page | ||
| 126 | |||
| 127 | Now, open any document in view mode and you will notice the nice "Hello" before your username. Follow the same process in order to override Javascript and CSS files ( http:~/~/localhost:8080/xwiki/skins/colibri/myfile.css ). | ||
| 128 | |||
| 129 | ==== 3. Overriding a skin resource ==== | ||
| 130 | |||
| 131 | 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 | ||
| 132 | |||
| 133 | * 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 | ||
| 134 | |||
| 135 | {{code}}/xwiki/resources/icons/silk/myicon.gif{{/code}} | ||
| 136 | for a resource found in the general resource directry, or | ||
| 137 | {{code}}/xwiki/skins/colibri/myimage.png{{/code}} | ||
| 138 | if the resource is specific to a certain skin, in this case 'colibri'. | ||
| 139 | |||
| 140 | * 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{{code}}icons/silk/myicon.gif{{/code}} | ||
| 141 | and in the second case simply | ||
| 142 | {{code}}myimage.png{{/code}} | ||
| 143 | * 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**. | ||
| 144 | * Create a file named as explained above and attach it to your Skin | ||
| 145 | |||
| 146 | {{info}} | ||
| 147 | **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: | ||
| 148 | |||
| 149 | {{code language="none"}} | ||
| 150 | .infomessage { | ||
| 151 | background-image: url("$xwiki.getSkinFile('icons/silk/information.gif')"); | ||
| 152 | } | ||
| 153 | {{/code}} | ||
| 154 | |||
| 155 | 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. | ||
| 156 | {{/info}} | ||
| 157 | |||
| 158 | === E. Adding new components to the Skin === | ||
| 159 | |||
| 160 | If you want to add new files to the skin, like CSS or Javascript files, you have two options: | ||
| 161 | |||
| 162 | * attach the files to the Skin document and reffer them by their URL, or | ||
| 163 | * add new properties to the (% class="sectionblockcodecolored" %)XWiki.XWikiSkins(%%) object from inside the Skin document, and refer them by their name | ||
| 164 | |||
| 165 | 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: | ||
| 166 | |||
| 167 | |||
| 168 | * Attach the CSS file to the Skin document | ||
| 169 | * Override the stylesheets.vm template and add the reference to your file in the template:((( | ||
| 170 | {{code language="html"}} | ||
| 171 | <link rel="stylesheet" | ||
| 172 | type="text/css" | ||
| 173 | href="$xwiki.getSkinFile('mynewfile.css')" | ||
| 174 | /> | ||
| 175 | {{/code}} | ||
| 176 | ))) | ||
| 177 | * Save the document | ||
| 178 | |||
| 179 | ((( | ||
| 180 | OR | ||
| 181 | ))) | ||
| 182 | |||
| 183 | ((( | ||
| 184 | * Add a new property to the XWiki.XWikiSkins, name it mynewfile.css, edit the Skin document's objects ( Edit -> Objects ), and paste the CSS code into the mynewfile.css field | ||
| 185 | * Override the Style component and add the following line to the content of the Style property:((( | ||
| 186 | {{code language="css"}} | ||
| 187 | @import "mynewfile.css"; | ||
| 188 | {{/code}} | ||
| 189 | |||
| 190 | |||
| 191 | |||
| 192 | 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 . | ||
| 193 | |||
| 194 | [[image:importCSS.png||style="border: 1px solid black; width: 650px;"]] | ||
| 195 | ))) | ||
| 196 | |||
| 197 | * Save the document | ||
| 198 | |||
| 199 | Open any document in view mode and you will notice that the stylesheet is now applied. | ||
| 200 | |||
| 201 | |||
| 202 | === F. Using images in a Skin document === | ||
| 203 | |||
| 204 | ==== 1. Changing the logo ==== | ||
| 205 | |||
| 206 | For example, if you want to add an image named myimage.jpg as being the logo for the current Skin, follow these steps: | ||
| 207 | |||
| 208 | * Attach the image to the Skin document | ||
| 209 | * Edit the document's objects | ||
| 210 | * Use the XWiki.XWikiSkins object and set the Logo property as being the name of the attached image myimage.jpg | ||
| 211 | * Save the document | ||
| 212 | |||
| 213 | Open any page in view mode and you will notice that the logo is now changed. | ||
| 214 | |||
| 215 | |||
| 216 | ==== 2. Adding images to the Skin interface ==== | ||
| 217 | |||
| 218 | To add images to the interface, attach them to the Skin document and use them in the CSS code. For example, if you want to use myimage.jpg as background image for the pages inside your XWiki Enterprise instance, follow these steps: | ||
| 219 | |||
| 220 | * Attach the image to the Skin document | ||
| 221 | * Choose one of these actions: | ||
| 222 | ** Add a new CSS component to the Skin, name it pagebackground.css and add a reference to it from the style.css component | ||
| 223 | ** Override the mybaseskin.css component (where mybaseskin is the name of the current Skin - for example: albatross.css, toucan.css or colibri.css) | ||
| 224 | * Paste the following code inside the CSS component:((( | ||
| 225 | {{code language="css"}} | ||
| 226 | body{ | ||
| 227 | background-image: url($xwiki.getSkinFile("myimage.jpg")); | ||
| 228 | } | ||
| 229 | {{/code}} | ||
| 230 | ))) | ||
| 231 | |||
| 232 | Open any page in view mode and you will notice that the the background of the page contains your image. Have fun taking advantage of the power of XWiki Skins! | ||
| 233 | |||
| 234 | == More about XWiki Skins == | ||
| 235 | |||
| 236 | 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 | ||
| 237 | |||
| 238 | == Further reading == | ||
| 239 | |||
| 240 | * the [[XWiki Data Model>>http://platform.xwiki.org/xwiki/bin/view/DevGuide/DataModel]] | ||
| 241 | * using the [[Skin Editor Application>>extensions:Extension.Skin Editor Application]] | ||
| 242 | * [[edit only one object>>http://dev.xwiki.org/xwiki/bin/view/Drafts/EditOneObject]] | ||
| 243 | ))) |
