On Thu, Apr 29, 2010 at 7:47 PM, Daniel Clark <[email protected]> wrote:
> IMHO would be more interesting to somehow integrate into fossil itself, > via something like https://mozillalabs.com/bespin/ - except make "the > cloud" instead "a fossil instance on my computer or another computer I > admin" - and of course glue / hook code. > If we could agree on JSON-based interfaces for outbound fossil data (e.g. timeline list, artifact details, etc.), and add the appropriate APIs, it would be relatively easy to build web-based GUIs which operate using either a CGI- or server-mode fossil in the back end. Getting a command-line version to work with json input would be more effort. e.g. via an interface like fossil json < jsonFileContainingCommandStructure e.g. the input json might look like: {"command":"timeline", "arguments":["-n",20]} (The fact that fossil is a monolithic app, and not a library+app, would make such an interface more difficult to implement.) To this end, i have investigated several C-based JSON libraries, but so far i have found nothing which particularly pleases me (in terms of licensing and API interface). That said, the JSON format is simple enough (and well documented enough) that writing a custom parser for it wouldn't be all that much work. (Maybe that's something for me to do this weekend.) One element of JSON which i can imagine (but am not certain) might be problematic in conjunction with fossil is that it is UTF-8 encoded, and i don't know if fossil handles UTF8. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
