Extension talk:EasyTimeline/archive

Great works! Yann 10:29, 28 Mar 2004 (UTC)

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) Actually it is indeed. Erik Zachte 00:30, 2 Jun 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)

I sure like what you're trying to accomplish here. Is it possible to use smaller time scales -- for example, could one use this to document the September 11 timeline? --Fjarlq 02:07, 26 May 2004 (UTC)


 * Not yet in a proper way. I will add other date/time presentation formats, once the project is well on its way. As a workaround you could input times as minutes since 12.00AM, using the years format, which is actually just 'whole numbers', and add texts like '4 PM' on a separate invisible bar at position 240, etc. But that would be difficult to input and maintain. Better keep this for later. Erik Zachte 04:20, 26 May 2004 (UTC)

I miss one thing here: Units om the time axis. E.g. "Year" in the case of soviet leaders, and "Million years" in the geological examples.


 * Well, 'years' for chart Soviet Leaders is little too obvious, don't you think? Or even still ambiguous unless I add calendar system :) Once the fixed png's have been replaced by the script based version I will add miilions years to geo timeline. Erik Zachte 01:53, 2 Jun 2004 (UTC)

I suggest moving this page simply to EasyTimeline.--Eloquence 04:48, 2 Jun 2004 (UTC)
 * Done, Erik Zachte 20:24, 2 Jun 2004 (UTC)

Issues

 * PHP parser converts < > into &amp;lt; &amp;gt; before ET is invoked
 * fixed


 * The current version does not yet support unicode. More on this at
 * Why not use -misc-fixed-*-*-*-*-*-*-*-*-*-*-iso10646-1 ? It has loads of unicode characters: Greek, Cyrillic, Thai, Runes ;-) See http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html -- en:User:Stw, 4pm 2004/05/31
 * I will add a 'Fonts = png:somefontname svg:someotherfontname' command. Any freetype compatible font (truetype etc) that is available on the server can then be used for png. For svg (not yet displayable in Wikipedia) rendering takes place on the client machine so anything goes there. Erik Zachte 23:27, 1 Jun 2004 (UTC)


 * Should dates be rendered newer above older, as they are now? On the one hand, latest events are arguably the most pertinent.  On the other, reading the chart chronologically is more natural if older dates are above newer dates.  Pgan002 05:48, 19 Jun 2004 (UTC)
 * Personally I liked the current style best, or maybe I just got used to it :). I will add an option to reverse the order in a future release. Erik Zachte 02:11, Jun 20, 2004 (UTC)

Bugs
For an example see (I did already "fix" the first bug, see the source.) -- en:User:Stw, 4pm, 31. May 2004
 * A label text that contains [dot] [space] [capital letter] will be converted to [dot] [space] [small letter]. Why?
 * [colon] [space] ... is converted to [colon] ...


 * Link within brackets (...) is not rendered properly. Erik Zachte 01:03, 2 Jun 2004 (UTC)