On Mon, Aug 6, 2012 at 11:46 AM, Jan Danielsson <[email protected]>wrote:
> 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. :) > Sorry, i didn't mean to imply that it was being deprecated. It is one of fossil's core features, and it DOES get used by many people, but not so much in the fossil project itself. (In fact, the wiki and CGI is what originally caught my eye in fossil.) > 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 > ...etc), and it would be too much hassle to use the embedded wiki system > for that. > It's certainly more convenient for that type of thing. > While I'm anyways on the topic of things which worry me a little.. > No worries - wiki is there to stay. Even if we wanted to (which we don't!), removing it would be a huge compatibility problem and would upset probably 30-50% of the users pretty badly ;). > 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. fossil wiki export ... fossil wiki commit ... > 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. > We DO have a wysiwyg editor on the list of todos, but it is pending the "custom pages" support because that support will include the infrastructure we need for serving the editor. i've been tinkering with the custom pages/commands support for 3-4 weeks now, but with my current approach (based on TH1) i keep running into a wall regarding what types of things we can reasonably do with th1. Over the weekend i had a nice chat with Joe Mistachkin about TCL, and i think the only reasonable way to do custom pages/commands (that is, without having to castrate them unduly) is to use his TCL support. Anwyay... -- ----- 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
