thanks Jürgen for bringing up the locking and mountig. I havent thought of those. Most of the other drawbacks of git are just features that we need not to use. I think that the ordinary user should not use bare (command line) git or svn commands.
As I said above the Difftool for FCStd will unlike produce 'patches' and the merge tool is going to be full FreeCAD (with GUI) that highlights changes and conflicts. I think producing human readable diffs (not just diffing the xml and brep files)
Code: Select all
part a was moved
part b was replaced by part c
the numerical value of constraint d in sketch e was changed from f to g
is something that's easy and can be started tomorrow. Whereas doing (automatic) merging is something one could write a thesis about
Going back to the Repository:
I think we should go on with the https://sourceforge.net/apps/mediawiki/ ... rk_project
define what information should be stored as metadata in the library and which could be available as well.
And then we can implement backends for the ressource framework.
And one of these backends would be a git repo, the next would use svn, another one would be the thingiverse api, and could be an interface to OpenPLM. And if those still don't fit our needs wee can still implement our version control system.