1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
<?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" type="topic" id="application-basics" xml:lang="gl">
<info>
<credit type="author">
<name>Allan Day</name>
<email>aday@gnome.org</email>
</credit>
<include xmlns="http://www.w3.org/2001/XInclude" href="legal.xml"/>
<desc>Características de aplicacións básicas</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>Básicos de aplicacións</title>
<p>These Human Interface Guidelines provide design guidance on the creation of GNOME applications. Given this focus on applications, this page provides a definition of applications from a user experience perspective. It also provides guidance on basic application behavior and characteristics.</p>
<p>The application model allows users to understand how software is distributed, installed and removed, as well as how that software behaves when in use. Ensuring that your software behaves according to this model will therefore help to ensure that it is predictable and conforms to user expectations. It will also ensure correct integration with system tools for installing and removing applications.</p>
<section id="application-definition">
<title>Que é unha aplicación?</title>
<p>A seguinte lista de características fornece unha definición básica dunha aplicación. Unha aplicación é unha peza distinta de software que:</p>
<list>
<item><p>Pode instalarse e eliminarse de forma individual dun sistema.</p></item>
<item><p>Non afecta nin interfire no comportamento doutras aplicacións.</p></item>
<item><p>Non depende doutras aplicacións para poder executarse.</p></item>
<item><p>Fornece cando menos unha <link xref="primary-windows">xanela principal</link>.</p></item>
<item><p>Ten un ome único e <link xref="icons-and-artwork#application-icons">icona</link>.</p></item>
<item><p>Ten un iniciador de aplicación.</p></item>
</list>
<p>A key theme in this definition is that applications are intended to be independent of other applications. This ensures flexibility, predictability, and simplicity of use.</p>
<p>Of course, there are other characteristics that are expected of applications, including standard window behavior, system integration, and application metadata. Guidance on these aspects of applications can be found elsewhere.</p>
<!-- Add a section on application launchers? -->
</section>
<section id="application-names">
<title>Nomeando a súa aplicación</title>
<p>An application’s name is vital. It is what users will be first exposed to, and will help them decide whether they want to use an application or not. It is a major part of your application’s public face.</p>
<p>Un nome de aplicación ten varias funcións:</p>
<list>
<item><p>Debe publicitar a súa aplicación a usuarios potenciais.</p></item>
<item><p>Debe servir como reforzo dunha identidade positiva, e ter cualidades expresivas.</p></item>
<item><p>Precisa identificar a súa aplicación nos sistemas nos que se instala e se executa.</p></item>
</list>
<p>Asegúrese que o nome da súa aplicación é curto — menos de 15 caracters. Isto asegurará que sempre se mostra o nome completo no ambiente de GNOME 3.</p>
<p>Additionally, choose an application name that is easy to understand and communicates your application’s functionality. Avoid references which will not be understood or be familiar to potential users, such as obscure cultural references, inside jokes and acronyms. Instead, pick a name that references what your application does, or the domain in which it operates.</p>
</section>
<!-- Possible additional section on defining scope. "A successful application does one thing, and does it well." -->
</page>
|
