This is a low priority, specially since I'm the only one who may see the need for this ;)
But the idea is to specify for each 'client' node where the media folder is. The media folder would have a subfolder per "project", named after the project name.
The idea is to streamline the process of dispatching the files to the clients. This is a separate issue, and a more complicated one, but media folders would help that.
From the original document:
"""
The XML file should include in the definition of each client/master a media folder. The media folder will store subfolders for the individual projects being ran into the VR-Lab. The projects informations are not included in the XML definition.
A project is a simple combination of .blend file, processor file and name. The Blender-VR Interface should allow the operator to add/remove projects. Remember that a single VR-Lab can run the same projects in different XMLs VR-Lab setups, and different projects in the same XML VR-Lab.
"""
This is a low priority, specially since I'm the only one who may see the need for this ;) But the idea is to specify for each 'client' node where the media folder is. The media folder would have a subfolder per "project", named after the project name.
The idea is to streamline the process of dispatching the files to the clients. This is a separate issue, and a more complicated one, but media folders would help that.
From the original document: """ The XML file should include in the definition of each client/master a media folder. The media folder will store subfolders for the individual projects being ran into the VR-Lab. The projects informations are not included in the XML definition.
A project is a simple combination of .blend file, processor file and name. The Blender-VR Interface should allow the operator to add/remove projects. Remember that a single VR-Lab can run the same projects in different XMLs VR-Lab setups, and different projects in the same XML VR-Lab. """