<?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" type="topic" id="visual-layout" xml:lang="gl">

  <info>
    <credit type="author">
      <name>Allan Day</name>
      <email>aday@gnome.org</email>
    </credit>
    <credit>
      <name>Calum Benson</name>
    </credit>
    <credit>
      <name>Adam Elman</name>
    </credit>
    <credit>
      <name>Seth Nickell</name>
    </credit>
    <credit>
      <name>Colin Robertson</name>
    </credit>
    <include xmlns="http://www.w3.org/2001/XInclude" href="legal.xml"/>
    <desc>Arranging elements within a user interface.</desc>
  
    <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>Visual layout</title>

<p>The visual layout of controls, information and content affects how easy it is to understand your application. As part of this, it is important to recognise that visual design has a strong impact on how much work is involved in using an application — poor layout results in users having to put in additional effort, while good layout requires less effort.</p>

<p>Good visual layout also obviously makes applications more attractive and visually pleasing.</p>

<p>Following these visual layout guidelines will help you to produce an application that is beautiful, easy to understand, and efficient to use.</p>

<section id="general-guidelines">
<title>Liñas de guía xerais</title>

<list>
<item><p>An alignment point is an imaginary vertical or horizontal line through your window that touches the edge of one or more labels or controls in the window. Minimize the number of these — the fewer there are, the cleaner and simpler your layout will appear, and the easier it will be for people to understand.</p></item>
<item><p>Align content and controls in your layout exactly. The eye is very sensitive to aligned and unaligned objects. If visual elements do not line up, it will be hard for someone to scan them. Elements that do not quite line up will be distracting.</p></item>
<item><p>Be consistent. Use the same amounts of spacing throughout.</p></item>
<item><p>Organize related controls and information into groups, and use spacing to differentiate them. This makes an interface far easier to read and understand.</p>
<list>
<item><p>As a rule of thumb, leave space between elements in increments of 6 pixels, going up as the relationship between related elements becomes more distant.</p></item>
<item><p>Between labels and associated components, leave 12 horizontal pixels.</p></item>
<item><p>For vertical spacing between groups of components, 18 pixels is adequate.</p></item>
<item><p>A general padding of 18 pixels is recommended between the contents of a dialog window and the window borders.</p></item>
</list></item>
<item><p>Indent elements by 12 pixels to denote hierarchy and association.</p></item>
<item><p>Avoid using frames with visible borders to separate groups of controls — use spacing and headers instead.</p></item>
</list>

<p>Incorrect spacing and alignment:</p>
<media type="image" mime="image/svg" src="figures/visual-alignment-incorrect.svg"/>

<p>Correct spacing and alignment:</p>
<media type="image" mime="image/svg" src="figures/visual-alignment-correct.svg"/>

<p>Correct spacing, with units (pixels):</p>
<media type="image" mime="image/svg" src="figures/visual-alignment-spacing.svg"/>

</section>

<section id="label-alignment">
<title>Label alignment</title>

<p>If possible, right-justify labels (see the diagram below). This will avoid large gaps between labels and their associated controls. This type of right-justification is not possible if you have indented controls: here left-justification should be used instead.</p>

<media type="image" mime="image/svg" src="figures/label-alignment.svg"/>

</section>

<section id="hierarchy">
<title>Visual hierarchy</title>

<p>Organize visual elements from top-to-bottom and left-to-right. This is the direction that people from western locales tend to read an interface, so that the items at the top-left will be encountered first. This ordering gives interfaces a hierarchy: those components that are viewed first are perceived to have priority over those that come after them. For this reason, you should place dominant controls above and to the left of the controls and content that they affect. Header bars are a key design pattern in this respect.</p>

</section>

</page>
