File: secondary-menus.page

package info (click to toggle)
gnome-devel-docs 40.3-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 79,188 kB
  • sloc: javascript: 2,514; xml: 2,407; ansic: 2,229; python: 1,854; makefile: 805; sh: 499; cpp: 131
file content (57 lines) | stat: -rw-r--r-- 2,843 bytes parent folder | download | duplicates (2)
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
<?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" xmlns:uix="http://projectmallard.org/experimental/ui/" type="topic" id="secondary-menus" xml:lang="gl">

  <info>
    <link type="guide" xref="patterns#primary"/>
    <desc>The application's secondary menu, denoted by three stacked horizontal dots</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>Secondary menus</title>

<media type="image" mime="image/svg" src="figures/patterns/secondary-menu.svg"/>

<p>Secondary menus are located in the header bar and include menu items for the current view or content item. This differentiates them from <link xref="primary-menus">primary menus</link>, which include menu items that relate to an entire application (such as <gui>Preferences</gui> and <gui>About "Name"</gui>).</p>

<section id="when-to-use">
<title>Cando usala</title>

<p>Secondary menus can be used to host controls that relate to a particular content item which is being displayed in the application window (such as a document, contact, conversation or photo). They are typically used in combination with in-window navigation or <link xref="sidebar-lists">sidebar lists</link>, since both these arrangements feature separate views or areas for content items to be shown.</p>

<p>Secondary menus are optional and only need to be used if there are enough controls to require a menu.</p>

</section>

<section id="guidance">
<title>Guidance</title>

<list>
<item><p>Secondary menus generally shouldn't reproduce menu items that are included in <link xref="primary-menus">primary menus</link>, like <gui>Preferences</gui> and <gui>About</gui>. However, it can sometimes be useful to show <gui>Help</gui>.</p></item>
<item><p>The <link xref="menus">standard guidelines for menus</link> can be followed when designing secondary menus.</p></item>
<item><p>A secondary menu is contained within a <link xref="popovers">popover</link>. As such, a header bar menu can include a variety of controls, such as groups of buttons.</p></item>
<item><p>Secondary menus shouldn’t include menu items for close or quit.</p></item>
</list>

</section>

<section id="api-reference">
<title>Referencia da API</title>

<list>
<item><p><link href="https://developer.gnome.org/gtk3/stable/GtkMenuButton.html">GtkMenuButton</link></p></item>
<item><p><link href="https://developer.gnome.org/gtk3/stable/GtkPopoverMenu.html">GtkPopoverMenu</link></p></item>
</list>

</section>

</page>