On 08/03/12 15:42, Stephan Beal wrote: [---] > Another consideration here is that the wiki has kind of fallen out of use, [---]
I don't know that that is true. The only proof of this I have seen prior to this thread is that at times it's mentioned that the fossil repository uses embedded wiki rather than the "built in" wiki. For my part, I use the "built in" editor/wiki command line on a daily basis, and it would sadden me greatly if it is depreciated, or if someone would scrap any ideas of enhancements to it due to the perceived notion that no one uses it any more. ...that said, I realize I could be the only one still using it. :) The embedded wiki is useful for pages which are versioned. But there are lots of things which I write which principally aren't meant to be "versioned", such as wide-perspective project goals, code conventions, security considerations, protocol requirements, etc. Things which are true in the past, present and future. I also have a central repository on a server which serves as "reference pages" (I collect notes on administration of things I very rarely do, cool/useful shell tricks, etc), and it would be too much hassle to use the embedded wiki system for that. While I'm anyways on the topic of things which worry me a little.. I travel by train a lot, and on the train I don't always have access to an electrical socket, so I run the laptop on battery. For this reason I often run without X (I want as good battery time as possible). Now, I don't want to come off as one of those "got off my lawn, you kids!" types, so I'll be very explicit: I'm 100% for all the AJAX:ish work being done and considered. It adds a lot of value to the users (including myself), so it should be there and continue to be worked on. That being said, I want to (as far as possible) be able to do what I do with fossil at home even when I'm working on the train, in console mode. This is the primary reason I would want markdown support (in the built-in wiki and ticket system): I think it's easier to read/parse (mentally) and write than any wiki syntax I've seen so far. And even if we get a nice WYSIWYG editor for the web interface (in theory rendering the stored format irrelevant), I'll still be sitting writing wiki documents on the train in plain old vim, because there really isn't any other option. -- Kind regards, Jan Danielsson
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
