Source file organization strategies, and use within Editor 8.0 Projects
During recent User Group meetings, a topic came up for discussion that is very important to consider for everyone interested in using Projects within MET/CAL Editor 8.0. Before importing or converting procedures to *.mc files for use within the new Editor, I recommend creating a "scratch" directory to use for testing and discovering how the Editor now stores procedures as text source files by default. Once you are comfortable with how the new Editor handles procedures as *.mc files, I recommend developing a strategy for how you want these files to be organized on your hard drive which complies with your company's quality system.
Many customers may elect to use subprocedures to maximize the re-use of procedure source code. Using a subprocedure to display your Copyright is an excellent example that I like to use. Here is an example of a directory structure that may help keep your source files organized, any or all of the layers can be optional:
By keeping common subprocedure code as universal as possible, the source files can be placed as high up the directory path chains as possible, and the code can be reused over and over again. This can decrease both development and maintenance time. Once the files are organized as desired, they can be added to any Editor 8.0 Project by right-clicking the Project within the Solution Explorer, then selecting Add > Existing Item (or use Shift+Alt+A). This creates a link to the existing file, and any edits will be saved to the original location. This also means that the next time any Project with a link to this same file is opened, it will reflect all changes made previously (e.g. the Copyright year). It is important to note that changes to the procedure *.mc files will not be reflected into those procedures are Published to a proc.dir, or a new procedure package is Published ( either *.pkm or *.pxe).
Please sign in to leave a comment.