On Fri, Jun 7, 2013 at 1:00 PM, Gilles <gilles.gana...@free.fr> wrote:
> Does someone know of a way to catch errors, if any, instead of parsing > the output returned by the application to figure it out? > Try to do so opens up a huge box of worms - we have no standards on how the output looks and it might be changed out from under you. The JSON API _might_ be able to do what you want, but it has limitations (e.g. no "commit" API except for saving wiki pages). The JSON API docs are here: https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/view and i've got a couple demo/proof-of-concept sites using it: http://fossil.wanderinghorse.net/repos/fwiki/editor/ as well as several actives wikis which live on top of a fossil repo but use the Google Code wiki format, e.g.: http://fossil.wanderinghorse.net/wikis/cson/ -- ----- 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
