On Wed, Feb 13, 2013 at 8:50 PM, Ross Berteig <[email protected]> wrote:
> While true that you primarily use JSON in CLI mode as a debugging aid, it > is a good tool for scripting fossil due to the much easier to parse output. > Extending JSON to cover some capabilities that require a checkout would not > harm the normal use of JSON as a remote API, and could aid those trying to > tame some of the more unruly human-readable output of the natural fossil > CLI interface. > i've been looking it over tonight, and the db_open_local() routine gives us most of what we need there - opening (if it can) or failing non-fatally (i.e. it returns false on error, as opposed to fatally failing). i'll experiment with a 'changes' command over the weekend - status_report() (in checkin.c) provides most of the logic, it just needs to be reworked a bit for JSON's purposes. -- ----- 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
