How would you want to use such a GUI? I mean practically what is a non-programmer user workflow that involves a VCS interaction via GUI?
The reason I ask, is that on several occasions I tried to convince "ordinary" users to incorporate a VCS into their daily tasks. Not just Fossil VCS, but Git and back in time SVN with GUI too. All of these attempts were unsuccessful, mainly due to lack of perceived utility. This gave me understanding that ordinary users deal with a different "revision" workflow than programmers. As the notion of a "project" often not clearly defined. Such users are often concerned with just a single Word document which then balloons to tie in a whole bunch of other resources. In such a setup a "change" representation is not what VCS's diff could produce. Also, there was not much of a need to retrieve previous states of such a document while the work is still in progress. Only after reaching a "final" version, such users would try to preserve the state before making "tweaks". This would be often done by creating a named copy (either of folder or just of TheFile). Collaborative use is slightly more convincing, yet even then the individual user workflow is still the same. The company backup policy takes over the VCS functions. Only one use-case, a "document tracking", was the most receptive. Mostly for the management and compliance convenience, not for the workflow. In such a case, tagging, searching and referencing were requested. So my feeling is that no amount of explanation or "instructions" would convert such users to make use of a VCS in any form, GUI or not. VCS would be perceived as an additional and annoying hoop to jump through. So I wonder, how do you see your use-cases and GUI VCS workflow? On Sun, Aug 5, 2018 at 3:55 PM, Gilles <codecompl...@free.fr> wrote: > Thanks for the info, but like 90% of deskop users, I run Windows. I gave up > on deskop Linux, even though I give it a try every year or so just to check > it out. > > I'm not arguing. It's just that Fossil is such a great SCM application that > I guess it would benefit even more users if it were available as a GUI > application instead of a CLI — which, I would venture, very few > non-developers, in this day and age, even know there is such as thing.) > > > On 05/08/2018 22:46, John Pateman wrote: > > Re Your point (2) > > There may not be a GUI for Windows (I don’t use Windows) but there is is a > nice ‘Tortoise-like’ GUI for Fossil on macOS - Snail Fossil. > > > On 5 Aug 2018, at 21:14, Gilles <codecompl...@free.fr> wrote: > > On 05/08/2018 22:02, Richard Hipp wrote: > > How does adding an extra component and a bunch of new interfaces make > a program easier to build? I think that the key to building complex > systems is to keep them as simple as possible. If you can omit a > DLL/shared library and all the maintenance and interface design > associated with it, then why wouldn't you? > > I was asking this naïve question because > 1. SQLite is a DLL + EXE package > 2. There's no maintained GUI for Fossil. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
