On Fri, 3 Aug 2012 15:42:05 +0200 Stephan Beal <[email protected]> wrote:
> > I do understand the rationale for this approach; if I were the > > author of Fossil (I'm incapable for this, but let's pretend I am, > > for the moment) I'd probably pick the same approach during an early > > phase of development. Now it seems that quite many users see > > overly simple markup capabilities of the Fossil's wiki engine to be > > a problem; a soultion exists and is even integrated. > Another consideration here is that the wiki has kind of fallen out of > use, with the embedded docs system generally being preferred. While i > admit that i pay a good deal of attention to fossil's wiki API (i've > added several of the wiki subcommands and the wiki API was amongst > the first of the JSON APIs added), i will admit that embedded docs > are generally a better solution. But the wiki is just too convenient > (which is the only reason anyone really uses a wiki, anyway). Once i > get embedded docs support in the JSON API, i probably won't touch the > wiki API again. My personal use case for Fossil's intergated wiki is a structured place to perform "brain dumps": that is, I have a problem to solve (and I'm writing code which is to solve it, hosting it using Fossil), and start to write down my observations on how to attack different parts of it, findings on the nature of the data I had to process etc. This fits the wiki paradigm rather well and does not really fit to the domain of the built-in documentation. Unfortunately, in my case I did have the need to use nested lists, convenient ways to insert multiline verbatim bits of text, and I'd love to have some (basic) support for tables (what ikiwiki has [1] would be just enough). Uploading images and inserting wiki links to them would also be a win for me (again, ikiwiki provides for this; this is called "attachments" in its lingo [2]). This would probably be an overkill for a markup engine built into Fossil, but I found myself wanting this feature more than once. Yeah, every time I think about this I do understand I could just create a page in my intranet ikiwiki instance an link to it from my Fossil's project's wiki page, but this kind of questions the whole point of having a built-in wiki engine. ;-) P.S. I'm constantly referring to ikiwiki because it stores all its content in a [D]VCS (Git in my particular case), and so does Fossil with its wiki engine. 1. http://ikiwiki.info/ikiwiki/directive/table/ 2. http://ikiwiki.info/plugins/attachment/ _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
