On Thu, Apr 3, 2014 at 3:37 AM, Andy Goth <andrew.m.g...@gmail.com> wrote:
> 1. With the potentially wider screen offered by a web browser, I don't see > a reason why the user and line number can't both be displayed. Can > annotate and blame be combined somehow? Perhaps offer magic JavaScript > checkboxes to show/hide the various columns (commit, date, time [not > currently shown], line number, user), and the default values of the > checkboxes will depend on whether annotate or blame was clicked. > The toggling of the user is actually not a bad idea, IMO. The _only_ think i don't like about it is that at some point (when Jan stops tinkering with the ignore-ws bits ;) i will blatantly steal (er... port) that into libfossil and i will need the ability to toggle that generation at the library-level (for clients who don't do JS). But that's my own problem, not fossil's. 2. The color palette is fairly limited, making it hard to visually > distinguish between nearby commits. I'd like to see a broader palette, for > instance using HSV rather than RGB interpolation. > Interestingly enough, this topic came up in a different form a few weeks ago. The explanation was that it's just intended to provide an overview, and not necessarily distinguish closely-timed commits. > 3. Colors are all set via <span style='background-color:#abcdef;'>. This > bloats the HTML and prevents my next suggestion. Instead emit some CSS in > the <head> to predefine the various span classes. > It's possible to edit the CSS (or HEAD block, for that matter) via the WWW UI. The reason the colors are embedded is because they're generated by a routine which is given a starting color, and ending color, and then it calculates an RGB value somewhere between that: http://fossil-scm.org/index.html/artifact/d9e9227f13aeb17b604b3c9daf81f7752480b5dd?ln=2190-2205 we cannot replace that with CSS unless we predefine ALL colors with CSS names. > 4. While any such spans are moused over, change the span's CSS so that all > instances of that span are somehow marked, e.g. with a special highlight > color like yellow. This should further help to distinguish between > versions and see which lines were changed by the same commit. > There is certainly more which could be done with hoverhelp, e.g. adding the checkin comment as hoverhelp for the user name or line number. > 6. Syntax highlighting. Just kidding, I actually don't want this, but I'm > sure somebody will ask someday. It _can_ be done without too much work with JS-side addons. i do something similar in this fossil-based Wiki which saves its pages in Google Code wiki format, serves them over the Fossil JSON API, and renders them on the client. The source blocks of this page, for example: http://fossil.wanderinghorse.net/wikis/cson/?page=TipsAndTricks -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But 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 fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
