If you do not, you will be forced to save the project in binary, that means completely overwriting every single method and your GIT repository. If you are a single user, this may not be so bad. But if you’re working in a team, this is going to guarantee code conflicts.
More than one of us here has been bitten by that bug
To clarify, if you lose your license, you can no longer save in Xojo Project or Xojo XML format (both text based formats).
Unfortunately, Xojo will let you open a Text or XML project and work on it, and when you go to Save it, you get prompted to save as a new Binary file, and at that point you are kind of screwed, as any editing changes you made will be lost.
@Jay_Menna : I don’t think you will accidentally wipe out your existing Text based files, is that what you are suggesting? In my experience the only risk is losing your edits since you opened the project.
I really wish Xojo had a better error message, something like this:
Warning: you are opening a Text-based project and your license doesn't support saving in Text based format. Either [Fix my license] or [Open in Read-only mode]
Edit to add: I don’t think this is specific to Git, it affects any Xojo developers using Text or XML based projects (which often used with Git, but may be used with Svn, Cornerstone/Svn, etc.)
Right, I do understand all of that, but, a Xojo project file - from my direct experience - is a file that github does not show you the code for, and has to be edited in Xojo… how does a whole team collaborate that way? I would imagine that multiple people working on different segments of the app file would result in each person’s file having different code. How would a branch pull work then? That is what I am trying to figure out.