On Mon, May 23, 2011 at 3:25 PM, Stephan Beal <sgb...@googlemail.com> wrote: > The most significant caveat, i think, is that because it's 100% > client-rendered, and fetching the pages requires processing JSON fetched via > AJAX, it does not degrade gracefully (at all) for "lesserly capable" > clients.
Very interesting project. Thank you for posting about it. I don't know about GoCo wiki syntax, but with most wiki syntaxes, it is somewhat human readable, so being 100% client side rendered is not that big of an issue. Being delivered as JSON is very significant. As I observed before, in the absense of Fossil delivering proper raw wiki source, Fossil does put the content in a div with class='content', so finding the content from Javascript on the client is fairly easy. If the wiki page is contained within nowiki, then the wiki page source is delivered as-is, so a client side wiki rerenderer could then extract the source from within the content division. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
