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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
<?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" xmlns:uix="http://projectmallard.org/experimental/ui/" type="topic" id="info-bars" xml:lang="gl">
<info>
<link type="guide" xref="patterns#secondary"/>
<desc>Application event notifications</desc>
<credit type="author">
<name>Allan Day</name>
<email>aday@gnome.org</email>
</credit>
<include xmlns="http://www.w3.org/2001/XInclude" href="legal.xml"/>
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
<mal:name>Fran Dieguez</mal:name>
<mal:email>frandieguez@gnome.org</mal:email>
<mal:years>2019.</mal:years>
</mal:credit>
</info>
<title>Info bars</title>
<media type="image" mime="image/svg" src="figures/patterns/info-bar.svg"/>
<p>An info bar is a strip that is placed above a content view, directly below the header bar or tool bar. It contains text, and can also include controls. Info bars persist: they can be permanent, or they can be dismissed by the user.</p>
<section id="when-to-use">
<title>Cando usala</title>
<p>Info bars can be used to communicate a particular state about a particular content item or location. For example, an info bar could indicate that a document is out of date or being edited by others, or that a service relating to a location is not operating. In some situations, they can also be used to present supplementary information, such as user guidance.</p>
<p>Since info bars are persistent, they are generally more appropriate for communicating ongoing states rather than events (<link xref="notifications">notifications</link> or <link xref="in-app-notifications">in-app notifications</link> are more appropriate here).</p>
<p>Info bars primarily communicate by using text, and have the advantage that they can include both a heading and a longer explanation. However, they also take up space and attract attention. If the state you want to communicate is not critical, or can be communicated through a simple string or icon, you might want to consider alternative approaches: text or icons can be added elsewhere in your interface, or the appearance of navigation controls (such as <link xref="view-switchers">view switchers</link>, <link xref="tabs">tabs</link> or <link xref="sidebar-lists">sidebar</link> lists) can be changed.</p>
</section>
<section id="guidelines">
<title>Liñas de guía</title>
<list>
<item><p>Beware of info bar overuse: they should be an exceptional presence in your interface.</p></item>
<item><p>Only one info bar should be visible at any one time.</p></item>
<item><p>Only include a longer explanation if it is really needed: a simple heading can often be sufficient.</p></item>
<item><p>Generally speaking, info bars do not require an icon.</p></item>
</list>
</section>
<section id="api-reference">
<title>Referencia da API</title>
<list>
<item><p><link xref="https://developer.gnome.org/gtk3/stable/GtkInfoBar.html">GtkInfoBar</link></p></item>
</list>
</section>
</page>
|
