The svg files produced by inkscape work great with git for history, but merging does not work. I wonder if that could be changed.
Steps to Replicate
Draw a line in inkscape, and save the .svg file in a git, and commit to branch-a.
Make a branch-b, draw another line, and commit.
Checkout branch-a, draw a line, and commit.
Merge branch-a and branch-b.
The result is a conflict, and the only way around it is to open the svg file in a text editor, and remove all conflicting id numbers. E.g.:
id="path10"
Proposed Feature
Have the resulting .svg files work with git, perhaps by giving random id numbers from a very large number set, making clashes unlikely.
Use Cases
Multiple people could make an image, or comic, with one doing line drawings, another correcting them, another doing shading, and a fourth adding text. The artists could later merge the branches together.
sad to see that nobody really shows interest in this. Having native git integration in inkscape would be an absolute killer feature. To date the biggest issue I face with any kind of design software is keeping track of files, files that branch off of other files etc.
I imagine a visual graph showing the current files previous versions and the branch its on and/or it's branches.
This would mean saving a file would be non destructive and if at a later point I realize that I need e.g. a previous version of an object (that I have since modified) I could just go to the file tree and jump to a previous save state pf my file.
Maybe to just copy out the needed object and then continuing where I left of or to branch out into a new direction with my file, building a cluster between related files so I don't have to go through my files, trying to figure out if file_3_ver2_rev5 or file_3_final or file_3_ver3 is the one I'm after.
ik this threads been dead for 3yrs however this is the closest of what I could find to what I'm after.
The svg files produced by inkscape work great with git for history, but merging does not work. I wonder if that could be changed.
Steps to Replicate
The result is a conflict, and the only way around it is to open the svg file in a text editor, and remove all conflicting id numbers. E.g.:
Proposed Feature
Have the resulting .svg files work with git, perhaps by giving random id numbers from a very large number set, making clashes unlikely.
Use Cases
Multiple people could make an image, or comic, with one doing line drawings, another correcting them, another doing shading, and a fourth adding text. The artists could later merge the branches together.
sad to see that nobody really shows interest in this. Having native git integration in inkscape would be an absolute killer feature. To date the biggest issue I face with any kind of design software is keeping track of files, files that branch off of other files etc.
I imagine a visual graph showing the current files previous versions and the branch its on and/or it's branches.
This would mean saving a file would be non destructive and if at a later point I realize that I need e.g. a previous version of an object (that I have since modified) I could just go to the file tree and jump to a previous save state pf my file.
Maybe to just copy out the needed object and then continuing where I left of or to branch out into a new direction with my file, building a cluster between related files so I don't have to go through my files, trying to figure out if file_3_ver2_rev5 or file_3_final or file_3_ver3 is the one I'm after.
ik this threads been dead for 3yrs however this is the closest of what I could find to what I'm after.