Tags : :
Github is a great way to organise an open source project. However, when sharing 3D models rather than code a key advantage is lost. Github cannont highlight speicfic changes to models in the same way it highlights changes to lines of code. Therefoer the only record of what changes are made are in the commit history; and this is subject to human error. Whatsmore it becomes very hard to merge changes, even if the changes are to seperate parts of the model.
Blender already has good data structure. Meshes, objects, materials etc. all have unique names and can be imported between blender files. The "Append" option allows all the data blocks of a .blend file to be browsed in a logical file structue. The challenge is to make this readable by GitHub so it can highlight changes in the same way it highlights changes to lines of code within files.
1. Github must be able to highlight changes to .blend files
- See problem section
- So no one is =10ptprevented from collaborating due to their operating system.
- To allow the solution to be used across all future Open Bionics development and any other collaborative 3D modelling projects.
Blender supports "Add-ons" and Github supports "Integrations". Potentially these features can be leveraged to provide a solution. Github has recently added the capability to view STL files so hopefully a similar path can be followed for .blend files.
Last Edited By: JonathanRaines Feb 2 16 5:27 PM. Edited 1 time