On Fri, Mar 30, 2012 at 10:20 AM, Stephan Beal <[email protected]>wrote:
> Even one step further: a given site can use multiple renderers as long as > it has a way of distinguishing wiki pages by type (e.g. by extension, > naming convention, or some marker tag in the first few bytes). e.g. it > could use MediWiki + Google Code + > PS: there's an example of that on this site: http://whiki.wanderinghorse.net/ http://whiki.wanderinghorse.net/?page=MarkDownTest http://whiki.wanderinghorse.net/?page=README.txt http://whiki.wanderinghorse.net/?page=test.js (in particular, read the last one) All four of those pages are rendered client-side using different renderers. That site uses a different back-end, but the fossil JSON API is actually based on that one, so the port is straightforward (tap the "Edit" button on those pages to see what i mean). That said, that particular back-end allows us to associate a content type with each page, which makes dispatching to a different renderer trivial. Fossil doesn't (directly) have that ability, though it could be faked with page naming conventions, storing wiki content as JSON object trees with more metadata, or (possibly) tags (i haven't tried that). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
