On Oct 9, 2012, at 13:30 , Joe Mistachkin wrote: > > Remigiusz Modrzejewski wrote: >> >> Actually... No. Fossil, with it's monolithic single-app design, is relatively >> hard to both extend and embed. >> > > I strongly disagree with this statement. Fossil is very extensible in the > classic Unix sense, by building command lines and parsing the resulting > output.
We both know how this compares to having an actual API... > Also, much work has been done, by myself and others, to make Fossil > extensible using Tcl. So, is it finally possible to script pre-/post- commit hooks? > Finally, Stephan Beal has done quiet a lot of work to make the JSON API a > reality, which enables quite a few useful extensibility scenarios. Yes, but his work would be much easier if it wasn't an afterthought. Plus, this is still a work in progress. Only once it is finished, and by that apart being functional I mean included in the official build and documentation, we can finally say that there is a Fossil API. > She has not been ignored. I have been assigned by Richard to help with > integrating > her work into Fossil and have been in direct contact with her. Also, you > may notice > the "markdown" branch in the official repository as of October 3rd, 2012. Oh, I missed that part. That's happy news to me :) Kind regards, Remigiusz Modrzejewski _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
