On Thu, Oct 6, 2011 at 1:56 PM, Gilles <gilles.gana...@free.fr> wrote:
> I tried WinFossil, but had issues with it. > It's not WinFossil's fault - because fossil has no well-defined standards for output format, it is a futile exercise to create a UI around it. One of the niches the JSON API hopes to fill is as a communication channel for front-ends like that one. > Any timetable for your product? > The "most important" functionality is working already (see the doc link). i unfortunately can't give a timetable - i hack on it as the time/energy/desire allow for. If you're well-versed in C, i'd be happy to have another developer or 3 working on these bits :). There are some (a small few) features which we can't provide over JSON without some major workarounds and/or caveats. Namely binary data (which JSON cannot natively support), which means committing binary files this way will not be implemented, at least initially, and will have some significant limitations if it is ever implemented (e.g. the RAM cost of committing base64-encoded binary content in JSON form would be roughly 2-3x the original content size, so it would likely fail miserably for those people who think that having files >500MB in their repo is somehow a good idea). Live demo: http://fossil.wanderinghorse.net/repos/fossil-sgb/json/ The various buttons on that page give a good summary of what works right now (but note that the public demo user does not have full access, so some commands will tell you "access denied"). -- ----- 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
