On Thu, Mar 22, 2012 at 3:52 PM, Ephrim Khong <dr.khong+fos...@gmail.com>wrote:
> I'm also very interested in a demonstration backend for using a different > wiki markup language. http://fossil.wanderinghorse.net/repos/fwiki/editor/ (click on the README link in the left menu for details) That demo currently uses the fossil wiki parsing back-end, but now that the core is working more or less how i want, the next step is to add a client-side renderer (or multiples - we could use client-side rules to render different wiki pages differently). i hope to get a version done this weekend which uses the Google Code wiki syntax (my personal favourite). AsciiDoc sounds intriguing, though, and i will also be looking for a JS implementation of it. i have all the code to handle the client-side rendering, i just have to plug it in to the fossil back-end (it currently uses a custom back-end using a JSON API very similar to fossil's, and the port will be straightforward). breaks portability a bit, and doesn't sync the markup between the > repositories). Maybe including some (sandboxed) scripting language > interpreter in fossil would help - one could then change the markup script > similar to the Header/Footer/CSS. > AFAIK there is a branch which integrates jimtcl into fossil, allowing the full range of tcl features via the built-in th1 script language. i "thought" this had made its way to the trunk, but i don't remember for certain. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
