Hello,

I just  committed some  changes that  will allow  multiple blocks  to be
highlighted when using ln= as a query parameter:

http://www.fossil-scm.org/index.html/timeline?r=multi-block-highlight&nd&c=2015-03-06+07%3A39%3A09&n=200

Will someone  review the changes  and provide feedback? Make  sure there
are no performance problems introduced by my feeble SQL, etc...

Here's a demo:

http://fossil.bradfords.org:8080/artifact/3ec6b6f998248624?ln=1777,1779+1750-1757+1723..1737+1739,1746+1720.1721

I tried to  make it robust enough to handle  overlaps (e.g. 1,4+2,3 will
result in  simply highlighting  lines 1--4). But  all the  array indexes
scare me so I would appreciate someone reviewing that specifically.

Also,  I wasn't  certain  if there  should be  a  single character  that
divides multiple blocks.  Right now I'm demoing the plus  (+) which will
be  decoded to  a  space, but  maybe something  more  explicit would  be
better? I would have preferred to use comma but the comma was already in
use as a  range delimter. Before making  this change I had  no idea that
ln= supported comma, dash and zero or more dots as delimiters.

Thanks,

Andy
-- 
TAI64 timestamp: 4000000054f96222


_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to