Hi, all, This is a bit off topic, but i thought it might interest a small handful of you...
We've had plenty of discussions about plugging in non-fossil wiki parsers to fossil. As far as i have been able to determine, the fossil CGI interface doesn't offer a way to return a raw, undecorated, unparsed wiki page (or any other file type, for that matter) to the browser for us to do custom parsing on. So... i wrote one. A wiki back-end, that is. The past couple days i've hacked together "whiki", a CGI/CLI hybrid app (like fossil) implementing a 100% JSON interface for the management of wiki content (listing, loading, and saving pages). It's intended to be used as the AJAX back-end for remote editor/viewer clients. whiki's code is hosted in fossil, but whiki is-a wiki, so i'm hosting whiki's wiki in whiki, but its code in fossil. The live demo is here: http://fossil.wanderinghorse.net/demos/whiki/ Saving won't be enabled unless you can guess the login info, though. i don't yet have an option to allow anonymous edits. That demo uses GoogleCode-formatted pages, but the underlying JSON framework is ignorant of the format and can host/serve arbitrary formats at the same time. The wiki entries each have a contentType field and a given front-end can support any number of formats it cares to. i.e. if you've got a MediaWiki parser for JavaScript then it would be easy to browse the wiki using that parser. Happy Hacking! -- ----- 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
