Notificaciones de eventos de aplicaciones
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 información

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.

# Cuándo usarlas

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 other, 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.

Since info bars are persistent, they are generally more appropriate for communicating ongoing states rather than events (notifications or in-app notifications are more appropriate here).

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 view switchers, tabs or sidebar lists) can be changed.

# Guías

Beware of info bar overuse: they should be an exceptional presence in your interface.

Only one info bar should be visable at any one time.

Only include a longer explanation if it is really needed: a simple heading can often be sufficient.

Generally speaking, info bars do not require an icon.

# Referencia de la API

GtkInfoBar