On 28/02/17 10:56, Thierry Goubier wrote:
2017-02-28 16:43 GMT+01:00 Offray Vladimir Luna Cárdenas <offray.l...@mutabit.com <mailto:offray.l...@mutabit.com>>:Hi Thierry, What I'm using is the Fossil JSON API as described in [1]. Managing Grafoscopio documentation with it is pretty easy and yes I believe it could help in bringing a unified API across several repositories (I have not tested that though). [1] http://fossil.wanderinghorse.net/repos/fwiki/index.cgi/wiki/README <http://fossil.wanderinghorse.net/repos/fwiki/index.cgi/wiki/README> You probably intended [2], isn't it?
Yep, I meant that one. :-)
I wasn't thinking much about multiple repos, but it could be one target. I was just thinking that there was/is one attempt to have a close integration to github API over HTTP in Pharo, and that this effort would have to b partially redone for, say GitLab, or Bitbucket because git does not defines a HTTP API and every hosting company creates one, whereas in Fossil everybody uses the JSON API.
Ohh I understand now. Well is useful in both scenarios, and a showcase of the power of simplicity and being late in the game :-).
Cheers, Offray
