I would say that if you need per shot scene locations then you would want one in each shot level. Because then you would be using the workspace.mel to define the environment per shot. You might even consider having Project_name be a root workspace that define the asset location and other global locations, and then have each sequence or shot also be workspaces and then use the baseWorkspace setting of the workspace command to inherit. Im not sure if workspaces can be chained or not. Haven't tested. Maybe each workspace can first call baseWorkspace on its parent.
On Dec 4, 2011, at 3:11 AM, Erkan Ozgur Yilmaz <eoyil...@gmail.com> wrote: > In a project, where the folder structure is like: > > Project_ Name/ > Assets/ > Asset_Name/ > Model/ > Rig/ > ... > etc. > Sequences/ > Seq_Name/ > Shots/ > SH001/ > Fx/ > Lighting/ > etc. > SH002/ > Fx/ > Lighting/ > etc. > ... > > What is the best place to place the workspace.mel, should I have only one > under the project root, or should I have one for every shot and asset? > > What do you think? > > E. Ozgur Yilmaz > Lead Technical Director > Imaj Animation & VFX Studios > www.imajonline.com > eoyilmaz.blogspot.com > > Sent from my iPad > > -- > view archives: http://groups.google.com/group/python_inside_maya > change your subscription settings: > http://groups.google.com/group/python_inside_maya/subscribe -- view archives: http://groups.google.com/group/python_inside_maya change your subscription settings: http://groups.google.com/group/python_inside_maya/subscribe
