On Tue, May 17, 2016 at 2:22 PM, jungle Boogie <jungleboog...@gmail.com> wrote: > > If fossil had a more polished gui to move files and bring up boxes to > type in commit messages, it may be more popular too. As it is, most > fossil commands seem straight forward in my use cases. >
Some of my co-workers use Fuel (on Windows) as a front end GUI to Fossil. For some operations, it spawns fossil.exe. For other operations, it communicates with a running Fossil server (which it can spawn as "fossil ui $repo" if the user asks, or can use a separately launched Fossil server). For many users, it probably exposes too much of the way interacts with a Fossil server, but does make using Fossil easier. I've also heard of #Fossil (also Sharp Fossil), but never seen it as no one I work with uses it. Up until 2 years ago, our preferred IDE was SlickEdit, a commercial IDE that runs on Linux as as well as Windows. It has support for interacting with any command line VCS. This worked well for my co-workers and I. Unfortunately, the top open source IDEs (Eclipse, CodeBlocks, Jedit and a few others) seem to not support interacting with command line VCS and seem to be uninterested or unfriendly to the idea.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
