User talk:Robert W King
[User bio is in User:Your Name] Template:TOC-right
Timeline
I just noticed we were playing tag on the DNA timeline, I thought I was losing my mind ;) I discovered that the correct length is dependant on the width of the browser. That is why it is different on my browser compared to your browser. Did you try using a tables structure to build the timeline. One advantage of that would be the length of the cell on the left would vary proportionally with the timelines length. Chris Day 22:11, 10 April 2008 (CDT)
- see Template:Timeline/Sample --Robert W King 22:16, 10 April 2008 (CDT)
I noticed you were changing widths to be in terms of pixels rather than %-ages? I never like doing things in terms of pixels, because for those on very small or very large screens (I have some old laptops with 600 pixel screens, so I'm sensitive to this - not everyone around the world has the latest and greatest), it gives a bad look. What's the problem with using %-ages?
Also, I see you were manually bolding all the dates. Why not have an optional "date=" parameter to {{TLevent}} which does the bolding inside the template? That way if you want to change the look of timelines, you don't have to edit every page which uses them. J. Noel Chiappa 10:48, 11 April 2008 (CDT)
- As Chris pointed out earlier, the wordwrap in percentages causes problems with the stem either being too short or too long based on the width of the browser. Fixed widths turn out to be better, unless I can figure out a way to improve the stem. Also, there's other work to be done on the template which I just haven't got around to doing yet, with much improvements to be made. They're all on my mental list. I'm just rrrreeeallly slacking on it. --Robert W King 10:55, 11 April 2008 (CDT)
- I just thought of a problem having a data parameter; some entries are just one line, while some have one year and multiple things happen during that year, which involve having a list. You'll need a carriage return to begin the list, but if you include one by default, the event stuff will automatically be on the next line even if it's just a single entry. What I thought about doing was making it like so:
|-[date]-[event ]but I'm not entirely sure it's aesthetically pleasing. --Robert W King 11:27, 11 April 2008 (CDT)
- Too bad about the bugs. I wonder if it would make any sense to pass the %-age in as an argument, and then, inside the {{TLevent}}, convert it to pixels there? J. Noel Chiappa 14:43, 11 April 2008 (CDT)