Allan Day
aday@gnome.org
Alex Puchades
alex94puchades@gmail.com 2015
Daniel Mustieles
daniel.mustieles@gmail.com 2011 - 2015
Nicolás Satragno
nsatragno@gnome.org 2013
Benjamín Valero Espinosa
benjavalero@gmail.com 2011
Jorge González
jorgegonz@svn.gnome.org 2009
Rosa Elena Pérez
rozydicemiau@gmail.com 2014
Oscar Rafael Arachi
arachi910@gmail.com 2014 - 2015
Miguel Ajuech
miguel.ann.28@gmail.com 2014
Adrián Pérez Domínguez
adrian@aztli.org 2015
Celina Osorio Ochoa
chelinoska@gmail.com 2015
Dario Amigon Espinoza
daramigon@gmail.com 2015
Yenisei Ramírez Pérez
yeniseirape@gmail.com 2015
José Roberto Ramíres Mendoza
aczella@gmail.com 2015
Bernardo Sánchez Romero
b.sanchez.rom@gmail.com 2015
Emmanuel Márquez Juárez
resident3333@gmail.com 2015
David Romero Serrano
lemi136@hotmail.com 2015
Omar Garcia Guzman
garciag.omar91@gmail.com 2015
Edilberto Huerta Niño
edilberto.huerta0290@gmail.com 2015

# Barras de cabecera

Las barras de cabecera son un elemento horizontal común que se colocan en la parte superior de la ventana. Estas desempeñan una serie de funciones:

Controles de la ventana: las barras de cabecera permiten mover ventanas arrastrándolas, incluyen botones de control de la ventana (típicamente un solo botón de cierre), y proporciona acceso a un menú de controles de la ventana.

Encabezado: un papel clave de una barra de cabecera es proporcionar un contexto para el contenido de la ventana, ya sea a través de un conmutador de encabezado o de vista.

Controles: las barras de cabecera proveen un lugar para los controles clave, típicamente en forma de botones.

# Cuándo usarlas

Header bars are recommended for all application windows. They provide a number of advantages over the traditional combination of title bar, menu bar and toolbar, including a smaller vertical footprint, and dynamic navigation and mode changes (such as with selection mode).

Header bars are incompatible with menu bars. If your application already incorporates a menu bar, you should evaluate the alternatives suggested in these guidelines. See the menu bar guidelines for more details on this.

# Controles

Header bars can contain key controls for the window, which can be placed on the left and right-hand side of the header bar. Examples of these controls include buttons for navigating back and forward, search, and selecting content.

Ensure that your header bar only contains a small number of key controls - this will help users to understand the primary functionality provided by the window, and will ensure that the window can be resized to narrow widths.

If a window requires more controls than can be comfortably accommodated within the header bar, additional functionality can be included within a header bar menu.

# Header bars are dynamic

A header bar can - and should - update along with view or mode changes. This ensures that header bar controls are always relevant to the current context.

If the window includes multiple views (accessed through a view switcher), the header bar can include different controls for each view.

If the window incorporates navigation, different controls can be shown depending on the location displayed in the window itself. It is common to show a back button on the left side of the header bar when navigating.

# Additional guidance

A header bar should always provide context for the window it belongs to. This aids window identification, and clarifies what is displayed in the window itself. This can either be done by placing a heading in the center of the header bar, or by including a view switcher.

Arrange controls within the header bar according to the three alignment points described in the visual layout guidelines - left, center and right.

New and back buttons should be placed on the left side of the header bar.

Always ensure that there is room for a header bar to be dragged. This is necessary to enable windows to be moved or resized.