On Fri, Feb 03, 2012 at 08:33:41PM +0100, Stephan Beal wrote: > How much work would it be to put together a proof-of-concept sbsdiff > > colorizer? > > > The new diffs can't reliably be colored using JS because of potential > syntactic ambiguities. It would work "often" but not "always."
The sbs diffs come by a '<pre>' and the dump of diffs in text form, without any browser-friendly semantic information. I imagine that a similar look could be achieved with tags in the middle, instead of '<pre>', and CSS. Fossil knows the semantic information of any symbol it outputs at the time of sbs diff, and it could add or not add the tags depending on ui or console behaviour. Those tags could have meanings for the browser, so it could use CSS to make them look like Richard likes, or like others may like. Would this be enough? Maybe Richard also relies on some ability to 'copy-and-paste' that text, that thus could be broken using the tags. What's bad in using a combination of tags and css in the ui output? The code in fossil looks too complex for too little win? Or simply noone wrote it still? Regards, Lluís. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
