On Thu, Oct 6, 2011 at 12:02 PM, Gilles <gilles.gana...@free.fr> wrote:
> Thanks for the info. Out of curiosity, what do you mean by "monolithic > design", and why is it a problem to write a GUI? Fossil is a standalone application, not a C library of functionality. That means that in order to write a UI the only possibility you have is to parse the command-line output. Since fossil makes no guarantees about output format, it's basically impossible (or, long-term, futile) to try to create a UI in this way. This worked (barely) with CVS because CVS had well-defined output formats (where as fossil is more "free form" (which i happen to prefer, so that isn't a complaint)). The JSON API effectively adds a library interface (of a sort) to fossil, which allows other applications to call specific functions of fossil and get well-defined responses which are easily parsed (JSON format) and understood. For example, we can write a shell-like interface which communicates with a fossil instance over JSON, hiding the JSON bits from the user in the form of command-shell-style input and output. More infos about the JSON API (still incomplete, but can already do a good deal) can be found here: https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/edit?hl=en_US -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
