109 lines
8.9 KiB
HTML
109 lines
8.9 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="User interfaces" />
|
||
|
|
<meta name="abstract" content="A user interface is the part of a software product that your customer actually sees." />
|
||
|
|
<meta name="description" content="A user interface is the part of a software product that your customer actually sees." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdevelopingappsdesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsuserinterdeschklist.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagstextdatatransdesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagscodtec.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsuserinterfaceman.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsprogrammessagedesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsmenudesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagscommanddesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagscultconvappdesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdispfiledsgngide.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsprtfc3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagssrcfl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagscdradesignguide.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagslangwoutnlvsupport.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagshowtranschardta.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagscommanddesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdevelopingappsdeliver.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="rbagsuseint" />
|
||
|
|
<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>User interfaces</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagsuseint"><a name="rbagsuseint"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">User interfaces</h1>
|
||
|
|
<div><p>A user interface is the part of a software product that your customer
|
||
|
|
actually sees.</p>
|
||
|
|
<p>A user interface may include the layout of display screens or printed output,
|
||
|
|
displayed or printed text, commands, online help, and messages. A user interface
|
||
|
|
is also the part of a software product that you must either translate or make
|
||
|
|
cultural changes to for users in other countries or cultures.</p>
|
||
|
|
<p>The operating system provides specific
|
||
|
|
software functions to help you organize text from your user interface and
|
||
|
|
store that text in a library for easy translation. The operating system also
|
||
|
|
provides you with a user interface manager that provides a consistent user
|
||
|
|
interface. The user interface manager provides comprehensive support for defining
|
||
|
|
and running panels such as displays and online help.</p>
|
||
|
|
<p>This section provides guidelines that you can follow when designing a user
|
||
|
|
interface for an international application. You should apply these guidelines
|
||
|
|
early in the design process. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsuserinterdeschklist.htm">Checklist: User interface design</a></strong><br />
|
||
|
|
When creating a user interface with globalized support, you should follow some rules and guidelines.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagstextdatatransdesign.htm">Text translation design</a></strong><br />
|
||
|
|
There are some general tips in this topic to help simplify the translation of your textual material.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagscodtec.htm">Textual data code design</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsuserinterfaceman.htm">User interface manager</a></strong><br />
|
||
|
|
The i5/OS™ user
|
||
|
|
interface manager (UIM) is a part of the system that allows you to define
|
||
|
|
panels and dialogs for your application.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsprogrammessagedesign.htm">Program message design</a></strong><br />
|
||
|
|
A message can be predefined or immediate.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsmenudesign.htm">Menu design</a></strong><br />
|
||
|
|
Define your own menus on the system. There are three types of user-defined menus: display file menus, UIM (reference) menus, and program menus.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagscommanddesign.htm">Command design</a></strong><br />
|
||
|
|
The i5/OS™ operating
|
||
|
|
system allows users to define and create their own commands. To create a command,
|
||
|
|
you must first define the command through command definition statements. Then
|
||
|
|
use the Create Command (CRTCMD) command to process the command definition
|
||
|
|
statements to create the command definition object.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagscultconvappdesign.htm">Cultural-dependent design</a></strong><br />
|
||
|
|
Different countries have different standards that must be taken into account when developing an NLS-enabled application. This culturally sensitive information must be placed outside the program the same way as the textual data is handled.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsdispfiledsgngide.htm">Display file design</a></strong><br />
|
||
|
|
Application panels typically consist of the major elements in this topic.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagsprtfc3.htm">Printer file design and translation</a></strong><br />
|
||
|
|
Program-described printer files and externally described printer files are two types of printer files.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagssrcfl.htm">Source file design</a></strong><br />
|
||
|
|
Database source files are implicitly assigned the CCSID of the job when they are created, unless they have been explicitly assigned a CCSID value using the CCSID parameter on the Create Physical File (CRTPF) or Create Source Physical File (CRTSRCPF) command.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagscdradesignguide.htm">Character data representation architecture design</a></strong><br />
|
||
|
|
To enable your application for a multilingual environment, consider the information in this topic.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbagslangwoutnlvsupport.htm">Handle languages with no NLV support</a></strong><br />
|
||
|
|
If you need to support a language that does not have a supported national language version, follow the general steps in this topic.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsdevelopingappsdesign.htm" title="Your goal in designing international application components is to create components that support national languages independently.">Design globalized applications</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbagshowtranschardta.htm" title="Translating is changing the meaning of character data from a set of concepts, ideas, and statements in one human language to a culturally similar meaning in another human language.">Character data translation</a></div>
|
||
|
|
<div><a href="rbagscommanddesign.htm" title="The i5/OS operating system allows users to define and create their own commands. To create a command, you must first define the command through command definition statements. Then use the Create Command (CRTCMD) command to process the command definition statements to create the command definition object.">Command design</a></div>
|
||
|
|
<div><a href="rbagsdevelopingappsdeliver.htm" title="As you prepare to deliver your globalized application, you should consider how globalization issues might affect the ways that your customers install and use your application.">Deliver globalized applications</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|