Version Control / Interface Assets


#1

For large and/or long-running projects, I think it would be helpful to have version control. The Save As function seems to have some limitations, especially as it relates to Interface Assets - they either have to be grand-fathered into the new version, or there needs to be a reference outside of the local project file directory.

Since Interface Assets change independently of a version (they made need to change to accommodate new features AND the content will probably continuously change), I’d be in favor of storing Interface Assets outside of the IF system and allowing the developer to manually point an asset to a physical file.

Version Control (not auto backups) will be needed if complex or long-running projects need to publish periodic version upgrades (other than renaming the file).

  • I agree
  • I disagree

0 voters