67 lines
5.3 KiB
HTML
67 lines
5.3 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Textual data code design" />
|
|
<meta name="abstract" content="Application displays, printer file specifications, and user-created commands typically contain a large amount of constant text. Application displays, printer file specifications, and user-created commands also contain input and output fields such as headings, field prompts, instruction lines, and function key descriptions." />
|
|
<meta name="description" content="Application displays, printer file specifications, and user-created commands typically contain a large amount of constant text. Application displays, printer file specifications, and user-created commands also contain input and output fields such as headings, field prompts, instruction lines, and function key descriptions." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsuseint.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsearlymessagebind.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagslatemessagebind.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdircodeunnamedoutfld.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagstxtstoredindbfiles.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsconstanttextstrngs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsprtfc3.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbagscodtec" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Textual data code design</title>
|
|
</head>
|
|
<body id="rbagscodtec"><a name="rbagscodtec"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Textual data code design</h1>
|
|
<div><p>Application displays, printer file specifications, and user-created
|
|
commands typically contain a large amount of constant text. Application displays,
|
|
printer file specifications, and user-created commands also contain input
|
|
and output fields such as headings, field prompts, instruction lines, and
|
|
function key descriptions.</p>
|
|
<p>You can use different techniques to specify, store, and use constant text.
|
|
You can use each technique for specific types of textual data
|
|
components. Each technique has its advantages and disadvantages. </p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbagsearlymessagebind.htm">Early message binding</a></strong><br />
|
|
Text can be stored externally from the source code in a separate message file but is bound into the object when it is created.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagslatemessagebind.htm">Late message binding</a></strong><br />
|
|
Text can be stored externally from the DDS source code in a message description and is bound only to the display format at run time.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagsdircodeunnamedoutfld.htm">Direct coding as an unnamed output field</a></strong><br />
|
|
The most common way to define constant text is to specify the text directly in the source code as a literal. While this method is the most common way to define constant text, it is the most difficult to translate. Avoid using this method whenever coding an application, even if the application is not planned for translation.</li>
|
|
<li class="ulchildlink"><strong><a href="rbagstxtstoredindbfiles.htm">Text stored in database files</a></strong><br />
|
|
Text can be stored externally from the source code in a database file, retrieved by the application program, and then moved to the display or print format at run time.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsuseint.htm" title="A user interface is the part of a software product that your customer actually sees.">User interfaces</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rbagsconstanttextstrngs.htm" title="Because different languages have different space needs for the same expression, design your panels with this in mind.">Constant text strings</a></div>
|
|
<div><a href="rbagsprtfc3.htm" title="Program-described printer files and externally described printer files are two types of printer files.">Printer file design and translation</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |