Here is a random one.
I am working on a fairly large patch (really set of patches) with
another Max/MSP programmer, for various systems. In order to help
maintain sanity, we have started to use SVN (Subversion) for a
revision control system for our patchers.
For certain (valid, but I dont want to go into it) reasons, some of
our patchers do not have a file extension. When checking out patches
from our repository, our patches loose their association with Max/MSP
as their 'parent' app.
This is an issue as we are using certain apple scripts to check that
max is running, auto launch the app, and also using thispatcher
scripting and ubumenu's to auto-load assets off of disk, and this
gets fubar'ed without the associated metadata.
When using mxb or mxt formatted patchers without their
respective .mxb or .mxt extension, we loose our association and we
cannot open the files by double clicking or opening max and saying
file - open. If we use .mxt extension, we loose the icon and double
clicking the patch wont open Max, but selecting open from Max will
let it open,, if we use .mxb, we keep the icon and all works well.
Have other people run into this? Is this an issue with how mime-types/
file-types and creators work on OS X with resources, and SVN
stripping resource forks or .DS_Store files (or other magic hidden OS
X FS related BS), or is this something with our SVN servers file
system stipping the data, or a limitation of SVN itself? I searched
and noticed that SVN way back when had issues with this, but that
newer revisions supposedly fixed it. Is this a server side or client
Apologies for this (mostly) off topic post, but im curious how people
handle revision control when working with Max - and if anyone is
working sucsessfuly with SVN+ Max/MSP
We can try and re-formulate some things to use file types and
extensions on our end, but it would save lots of hours and money if
we can simply tell SVN to not strip any metadata.
v a d e //