[sldev] Automatically backing up scripts locally.

[Argent Stonecutter]

OK, I've looked at the COLLADA spec, and it doesn't seem to have  
anything to do with what I'm talking about here.

* The primitive object is a mesh, there's no mechanism to encode  
parametric geometry.
* There's no mechanism to encode the contents of objects.
* There's no mechanism to encode SL-specific content, such as scripts.
* There's no mechanism to describe the relationships between the  
backup and in-world assets.

The overall structure of region objects, region assets, object  
contents, and global assets represented by the files, directories,  
and symlinks would need to be retained. Not only doesn't COLLADA have  
any comparable structure, but also ince this is a mirror backup of  
ongoing work: this really would need to stay in the filesystem.

In addition, for the individual assets, about the only things for  
which the portable format would be useful would be textures,  
animations, and sounds. And these would be better off stored as tga  
or png files, bvh files, and flac files referenced by name from any  
COLLADA objects. Everything else would be in <extra> elements. It  
would be useful to include COLLADA descriptions of object meshes, but  
that wouldn't be used in restoring a backup.

I don't see COLLADA as being relevant, other than adding a  
"COLLADA.xml" file to each object directory, and maybe having the  
ability to select a set of objects and snapshot them... but it would  
really be more useful to make that a separate tool.