Las ventanas principales de su aplicación
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

# Ventanas primarias

Primary windows are the basic high-level container for your application user interface, and should present the core functionality of your application.

# Cuándo usarlas

Every application should have at least one primary window associated with it.

# Tipos de aplicaciones

There are two main models for primary windows:

## Aplicaciones con una única instancia

Single instance applications have a single primary window. This model is common for messaging applications, such as email, chat, or contacts.

## Aplicaciones con varias instancias

Multiple instance applications can have multiple primary windows. Typically, each primary window will be identical. Multi-instance applications are frequently viewers or editors, such as for documents or images.

Both single and multiple instance applications can allow multiple content items to be opened, either through the use of tabs or browser-style navigation. However, multiple windows do offer additional capabilities, which include:

Viewing several content items alongside each other.

Colocar contenido en distintas áreas de trabajo.

Organizing sets of content into different windows (if using tabs).

### Parent/child primary windows

Multiple instance applications typically have identical primary windows (in the case multiple web browser windows, for example). However, this is not always the case.

Primary windows can have a parent/child relationship. In this type of application, there is only ever one parent window. This typically contains an overview of content items which can be opened in the parent window, or in a separate child window. This allows multiple content items to be simultaneously open.

While child windows can only be opened through a parent window, they are not dependent on them in order to stay open: closing the parent window does not result in the closure of the application's child windows.

GNOME's Notes application is a good example of parent/child primary windows.

# Guías Generales

A single primary window should always be displayed when your application is launched.

If your application launcher is activated while your application is running, all its primary windows should be displayed.

La ventana principal debe contener la principal funcionalidad de su aplicación. No se base en diálogos o ventanas secundarias con el fin de preservar funcionalidades básicas.

Primary windows should be independent - closing one primary window should not result in other primary windows being closed.

Dialog windows should always be dependent on a primary window. See the dialogs page guidelines.

Your application should cease to run when all its primary windows have been closed.

The guidelines on display compatibility are particularly relevant for primary windows: be careful to ensure that they follow the advice on minimum display sizes, display orientation, and half-screen snap.

Quit should close all primary windows.

# Referencia de la API

GtkWindow

GtkApplicationWindow

GtkScrolledWindow