e2ecdcfe33
Former-commit-id:a02aeb236c[formerly9f19e3f712] [formerlya02aeb236c[formerly9f19e3f712] [formerly06a8b51d6d[formerly 64fa9254b946eae7e61bbc3f513b7c3696c4f54f]]] Former-commit-id:06a8b51d6dFormer-commit-id:8e80217e59[formerly3360eb6c5f] Former-commit-id:377dcd10b9
16 lines
1.3 KiB
HTML
16 lines
1.3 KiB
HTML
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="content-type"
|
|
content="text/html; charset=ISO-8859-1">
|
|
<title></title>
|
|
</head>
|
|
<body>
|
|
<center>
|
|
<h2> Text Formatter User Guide</h2>
|
|
<h3>19. Product set-up - Steps to Set-up Core Products</h3>
|
|
<hr>
|
|
<a href=Slide18.html>Previous Slide</a> <a href=Slide20.html>Next Slide</a> <br><img SRC=Slide19.JPG border=1><br></center>
|
|
<p><p><big>In this section, we will see the Inheritance Hierarchy in action as we set-up the core products. To set-up the core product, we first define a set of generic edit areas which some products require to run "out-of-the-box." Next we suggest reading the Standard file documentation to become familiar with the settings for the product. There are three versions of each core product: Baseline, Regional, and Site. All products come delivered in the BASE user directory with the Baseline and Regional versions already activated and available from the "Products" menu of the Local Formatter Dialog. The Site version must be activated by setting up a display name to appear in the Local Formatter dialog. Once activated, we can then run the product. At this point, we must customize the edit areas for for the local site. Finally, we verify that all three versions, Baseline, Regional, and Site run correctly with the customized edit areas.<br><br></big>
|
|
</body>
|
|
</html>
|