Skin Extension Tutorial (XWiki.org)

This tutorial demonstrates how to write a XWiki Skin Extension.

6

7

8

## $xwiki.ssx.use("$doc.fullName") ## Load the SSX object held in this document

9

10

11

= Introduction to XWiki Skin Extensions =

12

13

XWiki Skins eXtensions (abbreviated as **SX**) is a mechanism available in XWiki that allows to customize the layout of your wiki, or just some pages of your wiki, without the need of changing its skin templates and/or stylesheets. For this, the [[Skin Extension plugin>>extensions:Extension.Skin Extension Plugin]] (bundled in all XWiki Enterprise versions superior to 1.5) provides the ability to send to the browser extra JavaScript and CSS files that are not part of the actual skin of the wiki. The code for these //extensions// is defined in [[wiki objects>>platform:DevGuide.DataModel]].

14

15

This tutorial assumes that you already have basic knowledge of application development with XWiki. If this is not the case, we strongly advise you to start with the [[FAQ application tutorial>>FAQTutorialManual]] or the [[TODO application tutorial>>http://www.theserverside.com/news/1363830/XWiki-A-Platform-for-Collaborative-Apps]].

16

To illustrate usage of Skin Extension in XWiki, this tutorial will guide you through the creation of minimal JavaScript and StyleSheet working extensions. Then, will push it further to build a fully functional extension based on Natalie Downe's ##addSizes.js## script.

17

18

A minimal [[JavaScript>>http://en.wikipedia.org/wiki/JavaScript]] and [[CSS>>http://en.wikipedia.org/wiki/CSS]] knowledge is also needed to take full advantage of XWiki Skin Extensions, although expert knowledge in those fields is not needed to follow the tutorial.

19

20

21

If you are interested by the Skin eXtension mechanism itself and its internals, you should read its [[plugin page>>extensions:Extension.Skin Extension Plugin]], and its [[design page on dev.xwiki.org>>dev:Design.Skin Extensions]]. This tutorial does not address this topic. Or, since this is an Open Source project, feel free to {{scm path="xwiki-platform-core/xwiki-platform-skin/xwiki-platform-skin-skinx"}}browse the code{{/scm}}, and [[propose enhancements or improvements>>dev:Community.Contributing]].

22

23

24

= My first Skin eXtension =

25

26

Skin eXtensions are defined as [[XWiki Objects>>platform:DevGuide.DataModel#HXWikiClasses2CObjects2CandProperties]]. As a consequence, you can create them from your browser. Two types of extensions are currently supported: JavaScript eXtensions (incarnated by XWiki objects of class **XWiki.JavaScriptExtension**), and StyleSheet eXtensions (incarnated by XWiki objects of class **XWiki.StyleSheetExtension**). The very first step to create an eXtension is then... to create its object!

27

28

== Minimal JavaScript eXtension ==

29

30

=== Creating an eXtension object ===

31

32

Point your wiki on the page you want to create your extension in, and edit it with the object editor. The page itself can be any XWiki page - an existing page or a new page. I use in this example the page **XWiki.SkinExt**. From the **New Object** drop-down list of the object editor choose **XWiki.JavaScriptExtension**. Then, click the "Add" button.

The object editor is available only to [[advanced users>>platform:Features.PageEditing#HAdvancedMode]].

38

39

40

Once the page is loaded, you should see your extension object in the object list.

41

42

=== Writing the eXtension ===

43

44

Now that the object is available, we can just start writing the actual eXtension. For this, we will fill in all the fields of the created object. The first one is the extension name. This is easy! We can just write here **Hello World** (this information is only descriptive, it is not actually used by the SX plugin). The next field name is **code**, and this is where we will write the javascript code we want our extension to execute. This eXtension is supposed to be minimalist, so let's write something very basic here: a traditional greeting alert ;)

45

46

47

alert("Hello World!");

48

49

50

Now the next field asks us if we want this extension to be used **Always** or **On Demand**. We will explore all the differences between those two modes later in the tutorial, let us for now just precise we want it **On Demand**, which will force us to call the eXtension explicitly to see it executed.

51

52

Next thing our eXtension wants to know is if we want its content being parsed or not. This option allows to write **[[velocity code>>platform:DevGuide.Scripting]]**, for example to dynamically generate the javascript code to be executed. We did not write any velocity, so we can just say **No**. We will see later on an example of an extension with parsed content.

53

54

Finally, we can precise a **caching policy**, to tune the HTTP headers that will be returned with the generated javascript file. Let's not go wild, and chose the **default** one here :)

55

56

That's it ! our eXtension is production-ready ! It should by now look like the following:

//Note: the "code" area size has been intentionally reduced for this screenshot.//

61

62

=== Testing the actual extension ===

63

64

Let's now test the whole thing! Remember we chose that our extension should be used //on demand// ? Well, that's what we are going to do right now. For this we will make a call to the [[Skin Extension plugin>>extensions:Extension.Skin Extension Plugin]]. We can do it for instance in the wiki content of our extension page, or any other page. For this, we edit the target page in Wiki mode, and write the following:

$xwiki.jsx.use("XWiki.SkinExt")

Of course, if you did not use this page name for your extension, you should adapt it. Click "Save and View", et voila! If everything is fine, you should see the magic:

You may have noticed that the javascript alert displays before the document is fully loaded in the browser. This is actually expected! If you look close at the generated sources, you will see that your extension has actually been added in the HTML header as any other **.js files** from the skin: (comments added for this tutorial)

81

82

83

== Minimal StyleSheet eXtension ==

88

89

Good, we wrote our first javascript extension. But, we see things big and we already are looking forward to modify the graphical appearance of wiki pages using those eXtensions. That's what **StyleSheet eXtensions** are meant for. And the good news is that it just works the same as javascript extensions, the only difference being that the code written is **CSS code**.

90

91

Create a new page named **XWiki.MyFirstStylesheetExtension**. From the **New Object** drop-down list of the object editor choose **XWiki.StyleSheetExtension**. Then, click the "Add" button. We will name it **Blue Background**, give it a **default** cache policy, ask it not to parse the content, and write the following **code**:

#xwikicontent {

background-color: lightBlue;

}

=== How to use Velocity in parsed content ===

101

102

103

If you want to use the colors of your active ColorTheme you can check how to [[call those variables>>extensions:Extension.Color Theme Application#HUsingColorThemesvariables]].

104

105

106

Example for **XWiki.JavaScriptExtension** code:

107

108

{{code}}#set($cuser=$context.getUser())

109

#if($cuser=="XWiki.XWikiGuest")

110

alert("Hello guest");

111

#else

112

alert("Hello $cuser");

113

#end{{/code}}

114

115

will show different alerts for different users on page refresh.

116

117

118

Example for **XWiki.StyleSheetExtension** code:

119

120

{{code}}#if($context.getUser()=="XWiki.XWikiGuest")

121

#mainContentArea {

122

background-color: grey;

}

#else

#mainContentArea {

background-color: blue;

}

#end{{/code}}

will show different background colors for authenticated and anonymous users.

131

132

133

Velocity doesn't know about CSS. Everything that looks like a Velocity macro or variable is evaluated. So, undefined macros and

134

variables are printed as is. E.g. **#xwikicontent** will be used as CSS ID field, unless **xwikicontent** Velocity macro is defined.

135

136

Velocity is a template language, so when the Velocity code is evaluated the Velocity variables are simply substituted in the template by their values. So:

137

138

{{code}}alert(false);{{/code}}

139

140

works because **false*** is a literal boolean value in JavaScript.

141

142

Though:

143

{{code}}alert($xcontext.user);{{/code}}

144

145

will be evaluated e.g. as **alert(XWiki.User);** which will throw an exception unless **User** is a JavaScript variable previously defined, therefor you need to wrap the value in quotes, e.g.

146

147

148

alert('$xcontext.user');

149

150

151

Or even more, because the value coming from Velocity can contain characters that are not allowed in a JavaScript string

152

literal. So safest is to write:

153

154

155

alert('$escapetool.javascript($xcontext.user)');

== Put all together ==

161

162

Now let's try something new with this eXtension. Instead of loading it "On Demand", we can ask to have it used **"Always on this wiki"**. For this to happen however, you need to save the extension document with [[programming rights>>platform:AdminGuide.Access Rights#HSpecialpermissions]].

163

164

Your StyleSheet eXtension should now look like the following:

//Note: the "code" area size has been intentionally reduced for this Screenshot.//

169

170

It's time to test it. No need to call the SkinExtension plugin this time, this is the power of **Use Always** extensions, just click "Save and View" and see the SSX Magic. You can browse your wiki, all pages will be affected by your extension, for example the Main.WebHome page:

Note: if you want to use StyleSheet extension on demand, the principle is the same as for javascript, except that the plugin name is **ssx**, not **jsx**. Just make your call like this, and you are done:

$xwiki.ssx.use("XWiki.MyFirstStylesheetExtension")

A document can have as many **ssx** or **jsx** object as it needs, but a skin extension is identified by the name of the document, so in the end an extension is a document. The content of a skin extension is the concatenation of the objects in that document, so it's impossible to write two different extensions in a single document, only different parts of the same extension.

184

185

186

= Real-world eXtension with addSizes.js =

187

188

Let's now go further with this idea, and build a complete extension that will dynamically add the file type and size next to certain links that are present in a wiki document. This extension will make usage of the **addSizes.js** script published by Natalie Downe. This Javascript snippet itself relies on **json-head**, a Google App Engine application by Simon Willison which //"provides a JSON-P API for running [[HEAD requests>>http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4]] against an arbitrary URL"//. **addSizes.js** consumes this service to dynamically add the file type and size next to links in HTML documents. And this is what we will do in our new eXtension, using the aforementioned script and service.

189

190

Our new skin extension will be composed of a javascript and a stylesheet extension. We will hold the two objects in the same wiki page, namely **XWiki.AddSizesExtension**.

191

192

Once the document is loaded the javascript extension will be in charge of finding all the interesting links we want to decorate with sizes and file type icons, actually query for their size on the cloud, and finally inject this information next to each concerned link.

193

194

The stylesheet extension will just define the style we want for the extra size information that is injected next to the links.

195

196

The implementation below looks for the following file formats:

197

198

* OpenOffice.org Writer, Calc, and Impress (.odt, .ods, .odp)

199

* The most well known proprietary equivalents of the formats above

200

* Zip archives (.zip)

201

* PDFs (.pdf)

202

203

Of course, this can adapted to look for other formats that are relevant for your business :)

204

205

== Requesting and injecting files size with JSX ==

206

207

Our javascript extension will be composed of two code snippets. The second one will be the actual addSizes.js code, ported to work with Prototype instead of jQuery. The first one is a function needed by this portage.

208

209

AddSizes.js relies on the [[JSON with padding technique>>http://en.wikipedia.org/wiki/JSONP]] to query the **json-head** service, which is located on a different domain than the wiki, in a transparent manner. An alternative to this would be to have a similar service on the wiki itself (for example, in the [[groovy language>>platform:DevGuide.Scripting#HGroovy]]), and query it using a traditional AJAX request. [[Prototype.js>>http://prototypejs.org/]], the javascript framework bundled with XWiki, does not yet provide support for JSON-P requests. We will use for this a code snippet by Juriy Zaytsev written for this purpose. Let's first paste his code in a new **JSX** object, in **XWiki.AddSizesExtension** :

210

211

212

// getJSON function by Juriy Zaytsev

213

// http://github.com/kangax/protolicious/tree/master/get_json.js

214

(function(){

215

var id = 0, head = $$('head')[0], global = this;

216

global.getJSON = function(url, callback) {

217

var script = document.createElement('script'), token = '__jsonp' + id;

218

219

// callback should be a global function

220

global[token] = callback;

221

222

// url should have "?" parameter which is to be replaced with a global callback name

223

script.src = url.replace(/\?(&|$)/, '__jsonp' + id + '$1');

224

225

// clean up on load: remove script tag, null script variable and delete global callback function

226

script.onload = function() {

227

script.remove();

228

script = null;

229

delete global[token];

230

};

231

head.appendChild(script);

232

233

// callback name should be unique

id++;

}

})();

With this, we can now have a prototype version of addSizes.js. We can just paste this second snippet under the first one in the **code** are of our extension object, or add a new JavaScriptExtension object to the page (as SX combines all the objects of the same page into a single response):

240

241

242

// addSizes was written by Natalie Downe

243

// http://natbat.net/2008/Aug/27/addSizes/

244

// ported to prototype.js by Jerome Velociter, and adapted to XWiki for this tutorial

245

246

247

// http://www.opensource.org/licenses/bsd-license.php

248

249

Event.observe(window, 'load', function(event) {

250

$('xwikicontent').select(

251

'a[href$=".pdf"], a[href$=".doc"], a[href$=".zip"], a[href$=".xls"], a[href$=".odt"], a[href$=".ods"], a[href$=".odp"], a[href$=".ppt"]')

252

.each(function(link){

253

var bits = link.href.split('.');

254

var type = bits[bits.length -1];

255

256

var url = "http://json-head.appspot.com/?url="+encodeURIComponent (link.href)+"&callback=?";

257

258

getJSON(url, function(json){

259

var content_length = json.headers['Content-Length'];

260

if(!content_length) {

261

content_length = json.headers['content-length'];

262

}

263

if(json.ok && content_length) {

264

var length = parseInt(content_length, 10);

265

266

// divide the length into its largest unit

267

var units = [

268

[1024 * 1024 * 1024, 'GB'],

[1024 * 1024, 'MB'],

[1024, 'KB'],

[1, 'bytes']

];

for(var i = 0; i < units.length; i++){

275

276

var unitSize = units[i][0];

277

var unitText = units[i][1];

278

if (length >= unitSize) {

279

length = length / unitSize;

280

// 1 decimal place

281

length = Math.ceil(length * 10) / 10;

282

var lengthUnits = unitText;

break;

}

}

// insert the text in a span directly after the link and add a class to the link

288

Element.insert(link, {'after':

289

' <span class="filesize">(' + length + ' ' + lengthUnits + ')</span>'});

290

link.addClassName(type);

291

}

292

});

293

}); // each matched link

});

This is it! At this point, the extension should be already functional. If you test it now, you should be able to see the size of links getting injected next to matching each link in the content of a wiki document.

298

299

We will now make this information look nicer, and add an icon to represent the file type of the link, thanks to a stylesheet extension.

300

301

== Making it look nice with SSX ==

302

303

This time, we will take advantage of the **Parse** attribute of extensions that has been evoked upper in this tutorial. This way, we can be lazy and generate the CSS code using the velocity templating language, instead of writing a rule for each file format manually. Thanks to velocity and to the XWiki api, we will also be able to reference images attached to the extension document.

304

305

306

You can use XWiki global velocity variables **$doc**, **$request** and **$xcontext** in parsed content.

307

308

309

The class name that is added to each matching link by the JSX is actually the matching file extension itself (doc, pdf, etc.). Thus, we can then iterate over the extensions that we target, and generate a rule for each one of them. And more, if we name our icons with the convention of using the file extension, we can also reference the image within the same iteration.

310

311

You can [[download here>>attach:addSizesIcons.zip]] an archive with the set of icons used for this tutorial. The icons for MS products and for zip and pdf files are from the **[[Silk Icons Set>>http://www.famfamfam.com/lab/icons/silk/]]** by Mark James, under the [[Creative Commons Attribution 2.5 License>>http://creativecommons.org/licenses/by/2.5/]] license. To add the icons to your extension, just unzip the archive and attach them manually to your **XWiki.AddSizesExtension** document. Of course, you can also use your own set of icons. If you change the name of the files however, keep in mind you will have to adapt the stylesheet extension below.

312

313

Once you have the icons attached, create the stylesheet extension, set its parse attribute to **Yes**, and paste this code in the "Code" section:

314

315

316

/* A little padding on the right of links for the icons to fit */

317

#foreach($ext in ["odt","ods","odp","doc","xls","ppt","pdf","zip"])

318

#xwikicontent a.${ext} #if($velocityCount < 8), #end

#end {

padding-right:20px;

}

/* Files icons as background for the links */

324

#foreach($ext in ["odt","ods","odp","doc","xls","ppt","pdf","zip"])

325

#xwikicontent a.${ext} {

326

background:transparent url($doc.getAttachmentURL("${ext}.png")) no-repeat scroll right center;

}

#end

/* Nice spans for file size information */

331

#xwikicontent span.filesize {

332

font-size: 0.6em;

333

background-color:lightYellow;

}

When asked to serve the CSS file, XWiki will evaluate this code using its Velocity Rendering engine, and will return a file that contains pure CSS code!

338

339

== Testing the final eXtension ==

340

341

Ok, it's time for us to see the whole thing in action! The snippet below is intended to showcase the extension on its own wiki page. It request to the **jsx** and **ssx** plugins the use of the contained objects, and then give an example of all the supported links.

#set($void = $xwiki.jsx.use($doc.fullName))

346

#set($void = $xwiki.ssx.use($doc.fullName))

347

348

349

* [[An OpenOffice.org Writer document>>http://pt.openoffice.org/coop/ooo2prodspeca4pt.odt]]

350

* [[A MS Word document>>http://www.microsoft.com/hiserver/techinfo/Insurance.doc]]

351

* [[An OOo Spreadshet>>http://documentation.openoffice.org/Samples_Templates/Samples/Business_planner.ods]]

352

* [[Link to a MS Excel document>>http://www.microsoft.com/MSFT/download/financialhistoryT4Q.xls]]

353

* [[An OOo Presentation>>http://pt.openoffice.org/coop/ooo2prodintroen.odp]]

354

* [[Link to a MS Powerpoint file>>http://research.microsoft.com/ACM97/nmNoVid.ppt]]

355

* [[A great archive>>http://maven.xwiki.org/releases/com/xpn/xwiki/products/xwiki-enterprise-jetty-hsqldb/2.0/xwiki-enterprise-jetty-hsqldb-2.0.zip]]

356

* [[A PDF file>>http://www.adobe.com/motion/pdfs/sjsu_fumi_ss.pdf]]

357

358

359

Now there are two things to keep in mind :

360

361

* The browser must be able to reach the Internet, since the extension does need the help of the json-head service hosted on Google App Engine.

362

* As Natalie Downe wrote, //"this may not be 100% reliable due to App Engine being occasionally and unavoidably flakey"//. You may for example experience a long loading time (but since the extension triggers only once the whole wiki document is loaded, this will not penalize the wiki users).

363

364

In a future extension of this tutorial, we will address those two issues writing our own version of the json-head service on the wiki itself, using the [[groovy programming language>>platform:DevGuide.Scripting#HGroovy]].

365

366

Enough talk, let us see the result !

== Bonus: links to activate/deactivate the extension ==

[[image:bonus.gif]]

You can add this snippet in the wiki content of the extension document, and users with the programming right granted will be provided a link to activate or not the extension on all pages of the wiki:

#if($xwiki.hasAccessLevel("programming",$context.user)) ## Only programmers should be able to change the loading type

379

## otherwise, Always-used extensions will not work

380

381

#if($doc.getObject("XWiki.JavaScriptExtension").getProperty("use").value=="always")

382

#info("This extension is configured to be loaded on all the pages of this wiki.")