4 ms·
There's no reason a diagram can't be in source control. You just need a tool that can convert the diagram to code and the code to a diagram. You probably also w
by unityByFreedom 6y ago
There's no reason a diagram can't be in source control. You just need a tool that can convert the diagram to code and the code to a diagram. You probably also want to store the diagram's layout in textual form too so it can be converted back to the original human-created layout.
Then you can use git and optionally build custom tools like a visual diff of diagram v1 vs v2.
- tsimionescu 6y agoThe diff tool is the key here. Without that, there is no meaningful version control.
- unityByFreedom 6y agoWith a visual representation, diffing may be as easy as clicking next/previous between versions as you would images in an album. You could of course add more bells and whistles with highlighting.
- tsimionescu 6y agoSorry, I should have been more specific. When I say diffing tool, I mean one that can do what diff does - help Git do automatic merges, and help me do manual merges when auto merge finds conflicts. Two pictures side by side can do neither.
- unityByFreedom 6y agoI don't see why it couldn't be built. Git merge doesn't always do all the work for you, you still need to evaluate the changes.