From OpenWetWare

< OpenWetWare:Software | Extensions
Revision as of 17:35, 17 November 2007 by Bill Flanagan (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search



This is an extension to the Mediawiki package (you know, the thing you're using right now to view this page!) to allow you to embed Exhibits in a wiki page. Best of all, you can use data directly from tables right there in that page and others across the wiki. First you will need to make sure the wiki has the extension installed (See Installing Wibbit, for how to install it). Then, you will edit the pages that you want to put the exhibits in using the special syntax explained below.

Tables as Data

Exhibit is a way to display and deal with data. A standalone exhibit uses json files hosted along with the page the exhibit is on. Wibbit, in contrast, uses tables in wikis. The advantage of this is that anyone can edit the tables, so the data can be both edited and expanded easily and collaboratively. Also, visitors without Javascript have some access to the structured data.

The data, in turn, is composed of items, each of which has properties. For a fuller description of exhibit's data model, see its own wiki page. Here we will just explain the tabular wiki aspect of it.

Each item is represented by a row in the table. Each property of that item is a column. A page can have multiple tables which Exhibit can draw from, but any given table can only be used for one item type. So perhaps you could have an exhibit about historical literature. It might make sense to have one table for all the books with information like when it was published, who the author was, how many pages it has, etc. Then you could have another table for the authors, which would include information like when and where they were born and when and where they died, all the books they've written, and so on.

In order for exhibit to find the tables you want to use on the page you will have to give each an "id" to which you can refer to it. So the top of the 'authors' table might look like:

{| id="authors" |- !Name

or something like that.

All other schema data relating to authors and books is taken care of in the

Invalid language.

You need to specify a language like this: <source lang="html4strict">...</source>

Supported languages for syntax highlighting:

4cs, abap, actionscript, actionscript3, ada, apache, applescript, apt_sources, asm, asp, autoconf, autohotkey, autoit, avisynth, awk, bash, basic4gl, bf, bibtex, blitzbasic, bnf, boo, c, c_mac, caddcl, cadlisp, cfdg, cfm, cil, clojure, cmake, cobol, cpp, cpp-qt, csharp, css, cuesheet, d, dcs, delphi, diff, div, dos, dot, ecmascript, eiffel, email, erlang, fo, fortran, freebasic, fsharp, gambas, gdb, genero, gettext, glsl, gml, gnuplot, groovy, haskell, hq9plus, html4strict, idl, ini, inno, intercal, io, j, java, java5, javascript, jquery, kixtart, klonec, klonecpp, latex, lisp, locobasic, logtalk, lolcode, lotusformulas, lotusscript, lscript, lsl2, lua, m68k, make, mapbasic, matlab, mirc, mmix, modula3, mpasm, mxml, mysql, newlisp, nsis, oberon2, objc, ocaml, ocaml-brief, oobas, oracle11, oracle8, oxygene, pascal, per, perl, perl6, pf, php, php-brief, pic16, pike, pixelbender, plsql, povray, powerbuilder, powershell, progress, prolog, properties, providex, purebasic, python, qbasic, rails, rebol, reg, robots, rsplus, ruby, sas, scala, scheme, scilab, sdlbasic, smalltalk, smarty, sql, systemverilog, tcl, teraterm, text, thinbasic, tsql, typoscript, vb, vbnet, verilog, vhdl, vim, visualfoxpro, visualprolog, whitespace, whois, winbatch, xml, xorg_conf, xpp, z80

Personal tools