<page xmlns="http://projectmallard.org/1.0/" xmlns:uix="http://projectmallard.org/experimental/ui/" type="topic" id="info-bars" xml:lang="de">

  <info>

    <link type="guide" xref="patterns#secondary"/>

    <desc>Benachrichtigungen über Ereignisse in Anwendungen</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>Christian Kirbach</mal:name>

      <mal:email>christian.kirbach@gmail.com</mal:email>

      <mal:years>2014</mal:years>

    </mal:credit>

    <mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">

      <mal:name>Mario Blättermann</mal:name>

      <mal:email>mario.blaettermann@gmail.com</mal:email>

      <mal:years>2016</mal:years>

    </mal:credit>

  </info>

<title>Informationsleisten</title>

<media type="image" mime="image/svg" src="figures/patterns/info-bar.svg"/>

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.

<section id="when-to-use">

<title>Anwendungsfälle</title>

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 (<link xref="notifications">notifications</link> or <link xref="in-app-notifications">in-app notifications</link> 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 <link xref="view-switchers">view switchers</link>, <link xref="tabs">tabs</link> or <link xref="sidebar-lists">sidebar</link> lists) can be changed.

</section>

<section id="guidelies">

<title>Richtlinien</title>

<list>

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

<item>
Es sollten nicht mehrere Informationsleisten gleichzeitig sichtbar sein.
</item>

<item>
Verwenden Sie nur eine längere Beschreibung, wenn es unbedingt nötig ist: Eine einfache Überschrift sollte meist ausreichen.
</item>

<item>
Im Allgemeinen benötigen Informationsleisten kein Symbol.
</item>

</list>

</section>

<section id="api-reference">

<title>API-Referenz</title>

<list>

<item>
<link xref="https://developer.gnome.org/gtk3/stable/GtkInfoBar.html">GtkInfoBar</link>
</item>

</list>

</section>

</page>