> On Sep 29, 2017, at 2:46 PM, Andy Goth <andrew.m.g...@gmail.com> wrote: >> > > http://chiselapp.com/ comes closest in that it provides a web interface > for working on repositories as a whole. It does not provide what you > ask, nor do I know of any other web platforms that do.
Hey thats pretty cool, I was not even aware of that site! I am going to check that out, I guess that’s a decent way to keep a repo public, then I can clone it here locally for working on stuff. But that webui just looks pretty much like the same one built into the fossil binary, yes? Who is hosting that and what is the longevity compared to github and others? > > The trouble is that in order for a checkout user interface to be > meaningful, it needs to be bundled with tools to actually edit the > checkout files. Otherwise there's little point. From the perspective > of most programmers, web browsers can't compete with dedicated text > editors, so what you describe will likely not be successful in targeting > programmers. Primary interest right now is in using a headless machine that will be hosting a repo. And often users will not have command line access either. In the simplest case, I could set it up, with web ui access to the repo itself, but then always require them to clone the repo on another machine and do all their edits there and push their changes back to remote master repo. But it turns out there is also a use case for them being able to add files and commits to the repo directly on the headless linux box without having to clone the repo to another client machine. I hear what you’re saying about no way to edit without command line, but actually it would be perfectly fine to have the check out dir tree accessible via SMB share.. Then they can edit the files over SMB. But without command line access there is no way for them to commit the changes into fossil. That’s where a Web UI for some of those commands would be useful. But this could also be useful even when running fossil alone on a local desktop machine. Kind of like when you run “fossil ui” and up pops a web interface to the fossil repo on the local machine. Still edit the files with vi, etc, but the fossil UI basically accesses the DB right now…it doesn’t touch any checked out dir trees or provide any way to use the UI to do stuff on them….which is what I wish it could..then it could be a fairly platform independent checkout GUI….including over to headless linux boxes that might have a check out there also. > > One thing that could happen is for "fossil ui" itself to get more > checkout functionality, since it does indeed get used in combination > with checkout editing. Since it's used in conjunction with the command > line, it does not make any effort to replace the command line. But that > doesn't mean it can't be an alternative interface, just like how it > provides an alternative to diffing historical files from the command line. > The key is that it would have to become aware of specific dirs which have checkouts in them and then provide a view of that checkout..including uncommitted changes, etc.. > Personally I'm not interested in "fossil ui" performing the checkout > manipulations you describe, but nevertheless I would like it to be a bit > more aware of checkouts, e.g. to diff the current checkout with its > baseline check-in or other versions, to show the list of changes, or to > show and manage stashes. Right, well it would be great if we could see what exactly is GOING to be changed if we decide to commit, for example. Compare the working files in the checkout dir against what is in the DB…etc, etc.. those are just some of the simplest cases.. Ultimately I guess I will have to roll out my own, as I don’t think anything exists and I doubt there is much interest. I have a use case in the short term for something very simple that can at least just commit file changes to the repo through a webui. Basically need to be able to point the web ui at a .fslckout db and then enable the user to call commit, update, branch and a few other simple things. Having a file tree view of the actual dir tree would be useful too. Actually editing the files through the web, as you suggest, I don’t think would be that interesting to most people, but never know. I’d personally love to see an editor that could display a diff in realtime as I edit the file, so that as I edit the file I can see highlighting to show what I have changed compared to what is the repo, for example. Just one strange idea… but that isn’t the primary goal I’m asking for now just mainly want to be able to commit, update, changes, branch or a few basic operations against a .fslchkout where files have been updated over SMB somehow. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
