One thought that I had was to enable feeding wiki pages through a TCP pipe so that they could be post-processed. That would enable storing the pages in the wiki and rendering the wiki pages completely could be done on any platform that supports a web server. Any wiki markup can be supported and then fossil itself is not dependent on another library. If you don't want to use the extra markup, then don't. If you really feel the need for Markdown, Creole, etc, then it is available.
just my 0.02 //Bill On 11/29/2009 06:44 AM, Eric wrote: > The number of mails about this just proves that there is no right choice > for a new wiki markup. There are plenty of lightweight markup formats out > there (with their own enthusiastic followers) that haven't even been > mentioned here yet. If you want to do your project documentation a > particular way, then do it that way - as project files. The other problem > is introducing external dependencies for Fossil - have you noticed how few > there are? > > My vote (somebody else mentioned votes!) is to leave the Fossil wiki alone > (except for gradual improvement). > > > Eric > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
