subversion grasshopper .ghx files

Has anyone dared to try sub versioning ghx files? Sometimes there is some intense collaboration and it could be neat of changes can be committed/merged.

Replies to This Discussion

Permalink Reply by David Rutten on May 14, 2013 at 1:31am

Don't use GHX files. They are text based xml and merging them will almost certainly result in corrupt files (unless the changes are absolutely minimal like single properties of existing components).

You should use GH files as they will not be messed with by any program.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Joris Hoogeboom on May 14, 2013 at 3:57am

Yeah GH is on by default. I was just wondering about xml because it's text-based and thus might work the same as merging/forking/branching code.

It seems in principle the case but there is something that corrupts it rather quickly then it seems as you say. Seemed like a cool thing and I'm still wondering why specifically it would not work, I mean theoretically you could write the xml in a text-editor no?

Permalink Reply by David Rutten on May 14, 2013 at 7:59am

The xml has a value at the top that lists how many objects there are in the file. Let's say two people both add an object to an existing file. The count should be increased by 2, but merging them will only result in an increase of 1. That's the sort of problem you'll run into.

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS