On Fri, Sep 23, 2011 at 12:32 AM, Martin S. Weber <martin.we...@nist.gov>wrote:
> So the infrastructure is there now. All you need is to find and get a > client-side markdown (or whichever wiki dialect you prefer) library and > throw it at the content you're getting back from the json interface. > In fact, the wiki content doesn't _have_ to be plain text in this model. You can, e.g., store structured JSON documents. e.g. containing wiki text in their "content" field and the name of the renderer in the "contentType" or "renderer" field, and client-defined tags in another (array) field. In practice, the trickiest part of the client-side rendering is turning the wiki links into something usable by the application. But it's certainly doable (==has been done). And it inherits fossil's access roles, another feature my current back-end doesn't have. -- ----- 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
