source: LMDZ5/branches/IPSLCM6.0.11.rc1/tools/fcm/doc/design/code_management.html

Last change on this file was 1578, checked in by jghattas, 13 years ago
  • Add fcm in LMDZ5/tools directory

It is no longer needed to have fcm in your environement PATH variable.
Now makelmdz_fcm takes by default this fcm. It is still possible to use
another fcm, using -fcm_path argument in makelmdz_fcm.

File size: 2.1 KB
Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2
3<html>
4<head>
5  <title>FCM Detailed Design: Code Management System</title>
6  <meta name="author" content="FCM development team">
7  <meta name="descriptions" content=
8  "FCM Detailed Design: Code Management System">
9  <meta name="keywords" content="FCM, design">
10  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
11  <link rel="stylesheet" type="text/css" href="style.css">
12</head>
13
14<body>
15  <address>
16    <a href="index.html">FCM Detailed Design</a> &gt; Code Management System
17  </address>
18
19  <h1>Code Management System</h1>
20
21  <p>The code management commands provided by FCM are generally wrappers around
22  the underlying Subversion commands intended to add functionality or make the
23  system easier to use. Most of the wrappers are very simple and you can find
24  all the information you need from the <a href=
25  "../user_guide/command_ref.html">command reference section</a> of the FCM
26  User Guide and from the source code (which all resides within the Perl
27  package <a href=
28  "http://www-nwp/~fcm/FCM/src/lib/Fcm/Cm.pm"><em>Fcm::Cm</em></a>.
29  This section describes the few areas which merit further discussion.</p>
30
31  <h2><a name="prompts">Interactive Prompts</a></h2>
32
33  <p>Several of the commands prompt for further information interactively. This
34  is done using the function "&amp;main::get_input". This allows a different
35  version of the function to be used depending on the calling program. When
36  called by the main <tt>fcm</tt> script this function simply prompts for
37  information on the command line. However, when called from
38  <tt>fcm_gui_internal</tt> (which runs commands within the GUI) this function
39  uses a dialog box generated using Perl-Tk.</p>
40
41  <p>This design ensures that the main <tt>fcm</tt> command has no dependency
42  on the Perl <em>Tk</em> module.</p>
43
44  <h2><a name="merge">Merging</a></h2>
45
46  <p><em>Explain the logic used in determining the base path and
47  revision.</em></p>
48
49  <h2><a name="gui">GUI</a></h2>
50
51  <p><em>Anything needed here?</em></p>
52 
53  <script type="text/javascript" src="maintain.js">
54  </script>
55</body>
56</html>
Note: See TracBrowser for help on using the repository browser.