Joachim Langenbach > CAD-Firemen-0.5.3 > CAD::Firemen

Download:
CAD-Firemen-0.5.3.tar.gz

Dependencies

Annotate this POD

View/Report Bugs
Module Version: 0.5.3   Source   Latest Release: CAD-Firemen-0.6.2

NAME ^

CAD::Firemen - Scripts and Modules to manage PTC(R) Pro/Engineer(R) / Creo(TM) configurations. Use perldoc CAD::Firemen to get an introduction to the usage of this distribution.

VERSION ^

version 0.5.3

SYNOPSIS ^

This module provides 5 executables to help you manage your Pro/Engineer / Creo configurations. To display all new and removed options between releases, use fm_diff_cdb. If you want to check, whether an option is supported in an given release and which values can be assigned to this option, use fm_option_info. fm_diff_config allows you to analyze 2 config files and displays added, removed and changed options. This command can also be used to display changes of default values between to releases (see it's help). The command fm_check_config checks, that all option listed in given config are also known by the specified release. To complete the checks before releasing a new version of the config files use fm_check_struct, which checks a whole tree of files and directories, to make sure, that all referenced files within the config.pro are at there position (relative to the config.pro path). It also runs the same checks like fm_check_config does.

All scripts are much more usefull, if you create a database first, which contains options, their values and default value. Firemen provides the script fm_create_help, to create such a database. To create it, it uses the html help, so please make sure, that you have installed it in your wanted locale. Afterwards, you can use -d at all scripts to get more extended infos about displayed options.

To create an options database:

  fm_create_help -l de_DE

Compare all available options:

  fm_diff_cdb PATH_TO_DATABSE_1.CDB PATH_TO_DATABSE_2.CDB

To display changed default values and/or descriptions for each option, use

  fm_diff_cdb -d

Check whether option exists and display possible values:

  fm_option_info PATH_TO_DATABSE.CDB OPTION_NAME

Analyze the differences between 2 config files:

  fm_diff_config PATH_TO_CONFIG_1 PATH_TO_CONFIG_2

Check your config file:

  fm_check_config PATH_TO_DATABASE.CDB PATH_TO_CONFIG

Check a complete structure with config files, templates, ...

  fm_check_struct PATH_TO_DATABASE.cdb PATH_TO_STRUCTURE

METHODS ^

printVersion

Prints the version of bundled scripts and modules.

SETTINGS ^

The Fireman distribution uses a (YAML formatted) config file, where some global configs are stored. Actually it can look like this:

 ---
 databases:
   proeWildfire5.0: /options-proeWildfire5.0.sqlite
 defaultPath: D:\Program Files\proeWildfire 5.0
 paths:
 - D:\Program Files\PTC\Creo 1.0\Common Files\F000
 - D:\Program Files\proeWildfire 5.0
 defaultEnvironmentPath: e:\

Nearly all settings are handled automatically. Only the settings defaultPath, defaultEnvironmentPath and paths might be interesting for you. The first one contains one of the paths listed beneath. The path listed as defaultPath is used as the default value on the path selection screen. If Firemen is not able to detect all of your PTC installations (it uses the \$ENV{PATH} to detect them), you can add them to the paths section like the already listed ones.

AUTHOR ^

Joachim Langenbach <langenbach@imw.tu-clausthal.de>

COPYRIGHT AND LICENSE ^

This software is Copyright (c) 2011 by TU Clausthal, Institut fuer Maschinenwesen.

This is free software, licensed under:

  The GNU General Public License, Version 2, June 1991
syntax highlighting: