I just opened a recent AGS project's folder and I noticed that the script files appear as plain text files. It seems that they don't contain any binary gibberish anymore.
Is it true, or is it only by chance?
If so, Does that mean they can finally be edited using an external editor, without breaking the project files???
That would be awesome!
Here are guidelines to implement locking of important binary files (e.g. main game file, aka *.agf) in the SVN versioning protocol.
If you implement this, it means that your collaborators will be able to edit-modify-merge script files (aka *.ash, and *.asc), but not binary files. We'll see later for refinements on "what specific binary files types should be locked" (if you don't want to lock image files a.k.a. *.png or *.bmp, for example).
As soon as I'll have experimented myself, I'll produce a small tutorial, specifically written for AGS project managers.
=============================== PRINCIPLE =================================
You'd still have to enforce that all files have the svn:needs-lock property; not just the existing ones but newly added ones as well.
"svn autoprops" can do that but then you have to make sure that each client has the correct autoprops configuration.
This can done in the config file for every client (miscellany: enable-auto-props = yes, auto-props: *=svn:needs-lock). Check the client setting by a pre-commit hook on the server rejecting non-locked checkins .
============== IMPLEMENTATION WITH A SCRIPT (DIFFICULTY: AVERAGE) ==============
this script must be run on every client's machine, but at least it's out-of-the-box.
See it here: http://www.orcaware.com/svn/wiki/Automatic_lock-modify-unlock
====== IMPLEMENTATION USING THE "TORTOISESVN" INTERFACE (DIFFICULTY: EASY) ======
See the great tutorial here: http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-locking.html
=========================================================================