1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Dialogs</title><meta name="generator" content="DocBook XSL Stylesheets V1.65.1"><link rel="home" href="index.html" title="GNOME Human Interface Guidelines 2.0"><link rel="up" href="windows.html" title="Chapter3.Windows"><link rel="previous" href="windows-progress.html" title="Progress Windows"><link rel="next" href="windows-assistant.html" title="Assistants"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Dialogs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="windows-progress.html">Prev</a></td><th width="60%" align="center">Chapter3.Windows</th><td width="20%" align="right"><a accesskey="n" href="windows-assistant.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="windows-dialog"></a>Dialogs</h2></div></div><div></div></div><p>A dialog provides an exchange of information, or dialog, between the
user and the application. Use a dialog to obtain additional information
from the user that is needed to carry out a particular command or task.</p><p>A dialog should not appear in the panel window list.
Any open dialogs should be raised above the application when
the application window itself is selected from the window list.</p><div class="figure"><a name="id2531172"></a><p class="title"><b>Figure3.24.An example of a dialog</b></p><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="496"><tr style="height: 400px"><td><img src="images/tabbed-dialog-box.png" width="496" alt="An example of a dialog: the Glade project options dialog"></td></tr></table></div></div><p><b>Title Format:</b><i class="replaceable"><tt>Name of command that opened the dialog</tt></i>
(without any trailing ellipsis)</p><p><b>Window Commands:</b>Minimize, Roll-up/Unroll</p><p><b>Buttons:</b>Follow the guidelines for Alert buttons, see <a href="windows-alert.html#alert-button-order" title="Alert Buttons">the section called “Alert Buttons”</a>.</p><p>Your dialog may specify a default button, that is activated when the
user presses the <span><b class="keycap">Return</b></span> key. See <a href="windows-utility.html#default-buttons" title="Default Buttons">the section called “Default Buttons”</a> for guidance on choosing an appropriate
default button.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="dialog-buttons"></a>Additional Buttons</h3></div></div><div></div></div><p>You can include other buttons in a dialog's main button area
in addition to the affirmative button and <span class="guibutton">Cancel</span>,
but any more than one or two such buttons will make the dialog appear
complicated and difficult to use. As with any other button, keep the
labels as concise as possible to minimize this effect.</p><div class="itemizedlist"><p class="title"><b>Guidelines</b></p><ul type="disc"><li><p>Place buttons that apply to the dialog as a whole in the main
button area row at the bottom of the dialog, to the left of the
<span class="guibutton">Cancel</span> button.</p></li><li><p>Place buttons that apply to one or a few controls next to
their associated controls. For instance, place a
<span class="guibutton">Browse...</span> button at the trailing edge of the
text field it fills in.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="dialog-layout"></a>Layout</h3></div></div><div></div></div><p>A clean, logical dialog layout helps the user to quickly
understand what information is required from them.</p><div class="itemizedlist"><p class="title"><b>Guidelines</b></p><ul type="disc"><li><p>
Arrange controls in your dialog in the direction that people read.
In western locales, this is generally left-to-right, top-to-bottom.
Position the main controls with which the user will interact as close to
the upper left corner as possible. Follow similar guidelines for
arranging controls within groups in the dialog, and for specifying the
order in which controls are traversed using the <span><b class="keycap">Tab</b></span>
key.</p></li><li><p>
When opening a dialog, provide initial keyboard focus to the
component that you expect users to operate first. This focus is
especially important for users who must use a keyboard to navigate your
application.</p></li><li><p>Provide and show sensible default values for as many of the
controls in your dialog as possible when it is opened, so the user does
not have to generate the information from scratch. These defaults may
come from system settings (for example, hostname or IP address), or from
information that the user has previously entered in this or another
application (for example, email address or network proxy).</p></li></ul></div><p>See <a href="design.html" title="Chapter8.Visual Design">Chapter8, <i>Visual Design</i></a> for more detailed information on
arranging controls in dialogs.</p><p>See <a href="controls-notebooks.html" title="Tabbed Notebooks">the section called “Tabbed Notebooks”</a> for information on using
tabbed notebook controls in dialogs.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="common-dialogs"></a>Common Dialogs</h3></div></div><div></div></div><p>The gtk and GNOME libraries provide standard dialogs for many
common tasks, including opening and saving files, choosing fonts and
colors, and printing. Always use these when the user is performing one
of these tasks. You may modify the dialogs to reflect the needs of your
particular application (for example, adding preview
<span class="guibutton">Play</span> and <span class="guibutton">Stop</span> buttons to
the Open File dialog in an audio application), but do not change or
remove features so much as to make them unrecognizable.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="windows-progress.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="windows.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="windows-assistant.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Progress Windows</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Assistants</td></tr></table></div></body></html>
|
