Subject: Enforcing Project Standards 2003-12-10 - By Dobson, Jeff
Back
Not exactly answering your question, but just as a heads up, if put your
modified versions of out-of-the-box MEL scripts in a place that will have
loading priority over the default locations, you can more easily make the
jump between versions by keeping you customized stuff in a separate place.
For instance, if you put those scripts in \\Docs and Settings\username\My
Docs\Maya\5.0\scripts or any path that you might have setup with the
MAYA_SCRIPT_PATH environment variable it will take precedence over the
defaults.
-- --Original Message-- --
From: Chaney [mailto:chaney.interport@(protected)]
Sent: Tuesday, December 09, 2003 2:21 PM
To: maya-dev@(protected)
Subject: Enforcing Project Standards
Hello ,
I am setting up a system that enforces naming conventions and other
project standards . I have done this by editing the Maya scripts that
are called when saving , exporting , etc . This includes
"pv_perfomAction.mel" , "FileMenu.mel" , and more . All is working well
but I need to mindful to re-edit scripts between versions .
I was thinking that all of this could have been better handled with
a scriptJob or some "process" that listens for basic events such as
"save scene" , "export" , "addProject" , etc . Has anyone used this
latter approach or have thoughts on the best way to implement specific
projects standards ?
Thanks
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---
List-help: <mailto:listar@(protected)?Subject=help>
List-archive: <http://www.highend3d.com/maya/devarchive/>
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---
List-help: <mailto:listar@(protected)?Subject=help>
List-archive: <http://www.highend3d.com/maya/devarchive/>
|
|
