On Fri, Aug 9, 2013 at 11:31 PM, Themba Fletcher <[email protected]>wrote:
> Yep, that would work. I could also, since I was thinking specifically of > using the RSS feed, maybe cobble something together out of the JSON api -- > basically just a new version of timeline.rss with any "hidden" checkins > removed. Food for thought, thanks. > It might interest you to hack on libfossil, which will allow customized apps/mini-apps like that to be quickly thrown together. As a concrete example, here's a custom timeline implemented using the script bindings for libfossil: [stephan@host:~/cvs/fossil/f2/th1ish]$ ./th1ish timeline.th1ish -- -n=4 The 4 most recent timeline event(s) for /home/stephan/cvs/fossil/f2/.fslckout: ci @ 2013-08-09 23:20:24 [423842eb262c] by [stephan] in branch [trunk] doc updates w @ 2013-08-09 22:33:28 [7a2e57c50e8e] by [stephan] Changes to wiki page [home] ci @ 2013-08-09 22:29:49 [78bf9244bd16] by [stephan] in branch [trunk] Changed return semantics of fsl_list_reserve(), for consistency (old semantics were copy/pasted). Ran some code through reformatter. ci @ 2013-08-09 22:17:26 [f4e5795f9ec7] by [bch] in branch [trunk] buh-bye commented-out code. We've got version control here... The script looks like: http://fossil.wanderinghorse.net/repos/f2/index.cgi/artifact/b237bad93179931493968494feb043f6aa19e8d6 Anyway... -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
