Extension:EasyTimeline

As the saying goes: a picture often tells more than a thousand words. This is certainly true for graphical timelines. A detailed listing of events and dates in tabular form may offer the reader a lot of specifics, but may fail to provide an overview, a grand perspective.

From March 2004 there is wiki way to compose graphical time charts offline. A user writes an input script, runs EasyTimeline to generate the chart and uploads chart and script to Wikipedia. Someone else can download and modify the script, generate a new version of the chart, and upload the new chart and script back to Wikipedia.

See my project site for details.

Charts examples
Two simple examples of what is possible. For a much more extensive example (admittedly very crowded) see World War II - Asian Theatre.

Code example
Just to show you that the script syntax is reasonably intuitive: here is the script for the image to the left: Soviet Leaders.

April 10: Support added for clickable maps

The code example shown above already contains some wiki links. Wikipedia does not support these yet, but may do so in the foreseeable future. Try it at my project site.

Double and single brackets can be used like on wikipedia, language prefix is possible, e.g. more about foo. Single brackets for external links are also supported.

I propose to add the code on the image discussion page. See for an example on en:

Please add your comments.

Looks good. I'm going to tell about this to other Japanese Wikipedians now. :-) Tomos 00:11, 27 Mar 2004 (UTC)

I think it's a great idea! But, would it be possible to create a user-friendly interface, so that those who are less adept with code can use it? 154.5.51.173 01:12, 27 Mar 2004 (UTC)


 * Well, no programming skills are required, it is not really procedural code (no conditions, no loops), rather a strict set of rules on how to express oneself. A point and click, drag and drop interface would be nice, but I'll leave that to someone else, or maybe in a years time when I can't think of something else to do. Erik Zachte

The key feature missing from this are of course imagemaps to make the links clickable. I realize this is nontrivial, but if the script could generate the necessary maps, I could try to hack MediaWiki to support them (possibly even directly interface with a script, so that the user doesn't need to run it).

One other thing I noticed is that the smaller fonts are quite ugly. Anti-aliasing would help a lot here. SVG would, too.&mdash;Eloquence 01:22, 27 Mar 2004 (UTC)


 * Ploticus can create imagemaps, so EasyTimeline could get syntax for that, would be nice indeed.


 * Also creating SVG is just a change of parameter (they look better but are not viewable on every platform so should be offered as second option, like with international stats, they are also much larger in download size and take time to render on the client side, a fast PC may be needed).


 * PNG images can be included as well, I will add syntax for that in the foreseeable future.


 * Ploticus can support other fonts via freetype lib but this requires a rebuild with GCC, at least for Windows, (I haven't tried Linux version, but features should be cross-platform) see . I'm not familiar with GCC so haven't tried that. Erik Zachte


 * SVG support added. See example Erik Zachte

A wikier way of doing this would be to have the timelines updateable within the article (i.e. make the charts creatable online). So lets say there is a timeline, and someone wishes to add an element, they would update the PlotData area, and the software code would autogenerate the timeline. Just a thought DavidLevinson


 * Of course. Would be nice. Eloquence might be willing to pull that off. See above. Erik Zachte

Great job! Just a question. How to do with text only browser? Do you think a pure HTML version is feasible? (I mean only using and ) Which tag can we use for time line? ? A &#9774; ineko 03:35, 29 Mar 2004 (UTC)


 * Thanks. It will be difficult to translate all but the simplest diagrams into a text-only version that is still comprehensible. As for the geological example: I used the existing table at for the data, translating this back to three tables would make matters worse. I'll think about it though.


 * For tag look at new discussion on Extension Syntax that should lead to decision about this. Erik Zachte 10:41, 29 Mar 2004 (UTC)


 * The example you gave me, it's exactly what I thought about. If you can generate this kind of tables, it may be very great. I just wonder how a text browser may render this kind of table. If the rendering is buged, it is not necessary that you spend your time doing this feature. Or perhaps for saving image downloading time for slow connection.
 * About Extension Syntax, I done more than just looking ;o) I just wondered which tag name we can use for time line in case a "tag" syntax is choose. A &#9774; ineko 11:03, 29 Mar 2004 (UTC)