On Fri, 18 Oct 2013 11:48:20 +0200, Stestagg <[email protected]> wrote:

A very simple, low-budget way of improving the display would be to change
the CSS to make the dates more compact.

If you find the following section of the CSS and remove the font-size and
margin-top statements:

/* The "Date" that occurs on the left hand side of timelines */
div.divider {
  font-family: Georgia, serif;
  font-weight: bold;
  white-space: nowrap;
}

The timeline will be more compact

yes, thanks. I did something similar previously to my question. it helps but the "space inflation" (length of arrows between checkins) caused by the date boxes still is quite large (3-5). so it still would be nice to be able to inline the date.


Thanks



On Fri, Oct 18, 2013 at 10:40 AM, Stephan Beal <[email protected]>wrote:


On Fri, Oct 18, 2013 at 11:29 AM, Stephan Beal <[email protected]>wrote:

content, IIRC), but applying a CSS class (e.g. timeline-date) to those
fields (which currently don't have such a CSS tag) would allow one to


It turns out i just happened to look at the one DOM element which didn't
have such a class: most of the timeline DOM elements have CSS classes named
timelineSOMETHING, and the date fields now (as of 20 seconds ago) have a
'timelineDate' CSS class on them. With a bit of JS those can be manipulated in arbitrary ways, but note that any such manipulation might interfere with the canvas parts (the arrows and lines, which themselves are drawn onto an
HTML Canvas by JavaScript).


i _think_ the JS code and the C code are a bit intertwined/co-dependent
there, but i'll have to take a look at that before i can answer
definitively. In any case, i'll get some CSS markers added to the output so that this sort of customization is more feasible. i'm off work today, so
i'll get on this now.


The routines which output the timeline are, without a doubt, the most
complex in fossil (even more complex, in terms of amount of logic, than the core SCM internals, IMO). The routine which draws most of the visible parts
of the /timeline page, for example, is over 300 lines long, and it's
supported by several hundred more lines of code. Any sort of non-trivial
change here would be... well, non-trivial. There is another solution,
however, _if_ you're up for a bit of JavaScript programming. Here's an
example/proof-of-concept which uses the JSON API and a custom HTML/CSS/JSS
front-end to create custom timelines:

http://fossil.wanderinghorse.net/repos/fwiki/editor/fijet-scratchpad.html

If that might be an option for you, let me know and i can go into more
detail. (It could be integrated into the core UI, but that would be a bit
hackish... oh, but that gives me another idea to try out later.)

--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Since tyranny's the only guaranteed byproduct of those who insist on a
perfect world, freedom will have to do." -- Bigby Wolf

_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to