Very nice. My initial thoughts were to reproduce the existing fossil cmds but you are correct that this should not be the library's sole purpose.
On Mon, Oct 7, 2013 at 11:59 AM, Stephan Beal <sgb...@googlemail.com> wrote: > On Mon, Oct 7, 2013 at 5:27 PM, <sky5w...@gmail.com> wrote: > >> I guess the library interface is the target moving forward instead of >> forcing standardized output? >> > > Good question. Ideally the library will produce _no_ text output other > than the propagation of error messages from lower levels (e.g. messages > from the underlying sqlite3). So, no, it's not a goal of libfossil to > standardize any sort of output, but it is a goal to create a platform off > of which people who want to script it can create the output using whatever > format they like. For example, here's a proof-of-concept timeline mini-app > implemented using a script binding: > > > http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/artifact/2fb058d9936a9c237d23d2e2b3753f1c0cf4fb32 > > and here's a different one: > > > http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/artifact/649bf8fb8b17631eb7af6f9853969bd3a99b1b2b > > and here's one implemented in C: > > > http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/artifact/500b51d7b069974caaeb9b4783b0c7dbc3c5f082 > > the goal is, it would seem, almost the opposite of creating standardized > output, by creating a platform off of which one can ad-hoc their own > formats as needed. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
