On Fri, Aug 15, 2014 at 11:01 PM, Ron W <ronw.m...@gmail.com> wrote: > I recommend this because all Fossil version control features are available > to "embedded documentation" pages. The disadvantage is that editing the > requires using an external tool (though Fossil has a command for previewing > the pages (locally) before committing; the updated page would have to be > committed before other users could see it, but that's no different from > updating "built-in wiki" pages). >
Triva: that's one of the concrete use cases libfossil aims to solve. It requires the ability to create a commit given only partial content (one file) and without a checkout to work from, which is why fossil doesn't provide some basic UI for editing the embedded docs directly (as soon as it could, it would be able to edit arbitrary in-repo text files online). > 2. Use the "embedded documentation" pages as the published pages while > adds/updates are done on the "built-in wiki" pages. While this allows using > Fossil's web interface to edit wiki pages, currently only the most recent > version of a given page is view-able or update-able. (The changes are still > saved, just no easy way to access them.) > FWIW: Fossil's central wiki has been essentially abandoned in favor of embedded docs. Many people still use the wiki (and that was one of the two feature which initially attracted me to it), but for larger projects, with multiple devs, the embedded docs are superior to the wiki. > Anybody knows of something that allows tracking and answering tickets from >> a mobile phone ? >> > > Fossil's web interface is usable from a mobile phone or tablet that has a > web browser. > Thanks, Ron - that leads us nicely into a shameless plug... It's currently possible to use libfossil's script bindings to generate custom reports pages you need. Here's an example of a whole web site created using the previous-generation script bindings: http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/ the newer script engine is done and bound to libfossil, but the high-level CGI bits are incomplete: https://docs.google.com/document/d/13gRSl6-bj3LV-OKgE-BsqvqF33UFYW3oa3A2OJC5QSY/view libfossil doesn't currently have much explicit tickets support (because of their dependency on TH1), but the db layer gives one all the info he needs to create custom reports, e.g. these: http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/reports -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
