Stephan, I have been an active user of the JSON API and I have explored fossil as a backend for a distributed open data portal [1] (early alpha). So, I just want to say you thanks for your work, get well and give priority to your health. World needs generous, clever people and is important to have them well.
[1] http://smalltalkhub.com/#!/~Offray/Brea Best of luck with your operation on 2018. Take care and rest. Cheers, Offray On 12/11/17 09:45, Stephan Beal wrote: > On Sun, Nov 12, 2017 at 1:12 PM, <[email protected] > <mailto:[email protected]>> wrote: > > Good day to you all, > > I have been trying to find up-to-date information about the JSON API > built into Fossil. Is there any plans on moving forward with this? > > > i'm the original developer of the JSON API, but a severe, long-term > case of RSI (since Dec. 2014) has forced me to retire from my open > source work (except for occasional tiny patches), thus i don't > personally work on it any more. It's unclear if/when my damaged elbow > nerves will ever recover, so i can't make any code-related commitments > (my left elbow is still not fully recovered after an OP last May, and > i've got a second operation planned for early 2018 to try to alleviate > the problem in the right elbow). > > That's not to say that the JSON API is off-limits to other developers! > i would love to see someone take it over and actively work on it. > > > The latest information I could find is a link to a document on Google > Docs in a mail dated back in 2013 or so, and I cannot tell when the > document was last updated. The last time it was mentioned on the > official fossil-users mailing list was in March 2017 > > (https://www.mail-archive.com/[email protected]/msg24857.html > > <https://www.mail-archive.com/[email protected]/msg24857.html>) > but simply mentioned the same Google Docs document: > > https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/view > > <https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/view> > > > Those are still the current/complete docs. If someone has mutated the > JSON code such that it no longer matches those docs, i'm not aware of it. > > > Has this API been abandoned? > > > Not abandoned, just not currently actively developed. > > > It seems like a nice feature if you > want to develop a custom UI or application that uses Fossil as a > back-end, such as a full-blown wiki, for example. > > > That's exactly what i use the JSON API for. e.g.: > > http://fossil.wanderinghorse.net/wikis/cson > > that uses a custom front-end to server/manage wiki content from/in a > fossil repo. It uses client-side rendering using the GoogleCode wiki > format, rather than Fossil's built-in one. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > "Freedom is sloppy. But since tyranny's the only guaranteed byproduct > of those who insist on a perfect world, freedom will have to do." -- > Bigby Wolf > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
