On Nov 16, 2011, at 4:11 PM, Stephan Beal wrote: >> As a vcs yes. The ticketing system needs some setup to fit my taste, but >> that's not hard. But, sadly, the wiki is way too simplistic to be >> practical. But this probably will be resolved one day. >> > > Actually.... the JSON API is far enough along that a completely custom wiki > could be based on it, using one's own custom wiki syntax, provided a > client-side renderer is available for it. The user management and wiki APIs > are feature-complete enough to support this, and implementing a > proof-of-concept for this is on my (long) list of TODOs for the JSON API. > The only (IMO) significantly missing feature in this area is the ability to > get historical versions of the wiki pages - currently we only serve the > latest version in the JSON API (fixing that is of course also on the TODO > list).
Actually, I'm not sure if that's that good idea. This way you can bring client incompatibility, unless you mean writing in a better markup, but saving (and loading from) the plain Fossil thingy. It surely can be done, just is not as trivial as we'd like it to be. Kind regards, Remigiusz Modrzejewski _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
