Thanks for this - I'm definitely going to need it, and will try to make time to do some tests next week :)
On 27 September 2011 06:12, Stephan Beal <[email protected]> wrote: > Hi, all! > > With almost 90kb of new functionality and 21 pages of "draft spec" docs[1], > the JSON branch has reached a point where some of you might be able to get > some use out of it in your daily lives. > > But first, a quick public service announcement: as i mentioned in my first > "drum up support for JSON" post: if you do not comment/complain about the > JSON structures being returned by this API then i will end up making such > decisions by myself and you might not like them. So feel free to pipe up at > any time. Any and all feedback is considered (and it will be more strongly > considered if the corresponding code is not already written!). > > With that in mind... > > A summary of what currently works: > > - The core error reporting routines now format errors in JSON form when > running "in JSON mode" (==CLI 'json' command or HTTP /json path). > - Logging in and out, including the anonymous user, with or without > cookies. (We still have the 1 login/user limitation, though!) > - Wiki: list pages, create new page, fetch/save individual pages > - Branches: fetch list of all/open/closed branches > - Admin: list users, fetch a specific user > - Timeline: checkins, wiki, ticket ("before" and "after" search ranges > work, other options are pending) > - Misc.: server version info, repo stats, get current user's access rights, > "whoami" > - Access restrictions match the corresponding HTML-mode behaviours (and if > they don't, it's a bug). > - There's an ugly test/demo app and [an even uglier] > prototype/proof-of-concept wiki editor: see ajax/*.html or the live demo [2] > (caveat: on that site access is severely castrated, so you cannot test all > features). > > (Side note: relatively little core code was touched. Primarily the core > error reporting routines, a couple additions to the 'g' object, and the > parsing of POSTed JSON data.) > > All of the working features are documented in the working draft[1]. (Just > keep in mind that "implemented/working" doesn't necessarily mean "will still > work that way tomorrow"!) i update the doc as features are added/changed, so > check there or the commit timeline for updates. Once the API is more or less > complete i'll move the docs into the repo (where they philosophically > belong, but Google Docs is just way too convenient for the time being). > > The TODO list is still as long as my hair, and i seem to be adding two > TODOs for every feature added, so there's a ways to go, but the > functionality which is there appears to work fine and more is being added > all the time. All of the basic infrastructure is in place and has been more > or less stable for all of 2 or 3 days now, making it fairly easy to add new > JSON interfaces. > > Happy Hacking! > > [1] = "draft spec": > https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/edit > [2] = live demo (but no admin access for you!) > http://fossil.wanderinghorse.net/repos/fossil-sgb/json/index.html > > -- > ----- 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 > >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
