File: cha-checklist.html

package info (click to toggle)
ebook-dev-ggad 199908-2
  • links: PTS
  • area: main
  • in suites: woody
  • size: 2,264 kB
  • ctags: 1,163
  • sloc: sh: 44; makefile: 35
file content (251 lines) | stat: -rw-r--r-- 8,422 bytes parent folder | download | duplicates (2)
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
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
  <head>
    <title>
      Gnome Application Checklist
    </title>
    <meta name="GENERATOR" content=
    "Modular DocBook HTML Stylesheet Version 1.45">
    <link rel="HOME" title="GTK+ / Gnome Application Development"
    href="ggad.html">
    <link rel="UP" title="Building a Gnome Application" href= 
    "build-app.html">
    <link rel="PREVIOUS" title="Convenience Routines" href= 
    "sec-dialogs-convenience.html">
    <link rel="NEXT" title="Advanced GTK+/Gnome Techniques" href= 
    "advanced.html">
  </head>
  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink= 
  "#840084" alink="#0000FF">
    <div class="NAVHEADER">
      <table width="100%" border="0" bgcolor="#ffffff" cellpadding= 
      "1" cellspacing="0">
        <tr>
          <th colspan="4" align="center">
            <font color="#000000" size="2">GTK+ / Gnome Application
            Development</font>
          </th>
        </tr>
        <tr>
          <td width="25%" bgcolor="#ffffff" align="left">
            <a href="sec-dialogs-convenience.html"><font color= 
            "#0000ff" size="2"><b>&lt;&lt;&lt;
            Previous</b></font></a>
          </td>
          <td width="25%" colspan="2" bgcolor="#ffffff" align= 
          "center">
            <font color="#0000ff" size="2"><b><a href="ggad.html">
            <font color="#0000ff" size="2"><b>
            Home</b></font></a></b></font>
          </td>
          <td width="25%" bgcolor="#ffffff" align="right">
            <a href="advanced.html"><font color="#0000ff" size="2">
            <b>Next &gt;&gt;&gt;</b></font></a>
          </td>
        </tr>
      </table>
    </div>
    <div class="CHAPTER">
      <h1>
        <a name="CHA-CHECKLIST">Gnome Application Checklist</a>
      </h1>
      <p>
        Almost all Gnome applications should support a common set
        of features. This checklist summarizes the most important
        ones. Always remember: Gnome is a direct response to the
        problem of application heterogeneity in the X environment,
        and one of the most important goals of any Gnome
        application should be look-and-feel consistent with other
        Gnome applications, starting with the source code seen by
        programmers and ending with the spiffy GUI you present to
        users.
      </p>
      <ul>
        <li>
          <p>
            Create a standards-compliant source tree. Use the Gnome
            <tt class="APPLICATION">autoconf</tt> macros, or the
            <tt class="FILENAME">gnome-config</tt> script, to
            reliably locate the Gnome libraries and header files.
          </p>
        </li>
        <li>
          <p>
            Include a <tt class="FILENAME">README</tt> describing
            the package.
          </p>
        </li>
        <li>
          <p>
            Include the standard <tt class="FILENAME">INSTALL</tt>
            file describing how to compile and install the package;
            change the standard file to reflect anything specific
            to your application.
          </p>
        </li>
        <li>
          <p>
            Include a copyright, in a file called <tt class= 
            "FILENAME">COPYING</tt>.
          </p>
        </li>
        <li>
          <p>
            Internationalize your application with GNU <tt class= 
            "APPLICATION">gettext</tt> and the standard C library
            functions.
          </p>
        </li>
        <li>
          <p>
            Include the <tt class="FILENAME">intl</tt> directory
            with your application, so users can build the
            application without having <tt class="APPLICATION">
            gettext</tt>. Include <tt class="FILENAME">intl</tt> in
            your header file search path.
          </p>
        </li>
        <li>
          <p>
            Define the <tt class="APPLICATION">G_LOG_DOMAIN</tt>
            preprocessor symbol to identify the origin of glib
            error messages.
          </p>
        </li>
        <li>
          <p>
            Define the <tt class="APPLICATION">GNOMELOCALEDIR</tt>
            preprocessor symbol so Gnome can find translation
            files.
          </p>
        </li>
        <li>
          <p>
            Install a <tt class="APPLICATION">.desktop</tt> file so
            your application will appear on the Gnome desktop's
            menus.
          </p>
        </li>
        <li>
          <p>
            Install help files along with <tt class="FILENAME">
            topic.dat</tt> files so the Gnome help browser can
            locate them.
          </p>
        </li>
        <li>
          <p>
            Be sure the <tt class="APPLICATION">make distcheck</tt>
            target works; this is will catch many common makefile
            errors.
          </p>
        </li>
        <li>
          <p>
            Set up a <tt class="APPLICATION">popt</tt> argument
            parser; at a minimum, you will probably want to support
            a <tt class="APPLICATION">--geometry</tt> option.
          </p>
        </li>
        <li>
          <p>
            All configuration should be possible via the GUI; the
            easiest way to achieve this is with the Gnome
            configuration library.
          </p>
        </li>
        <li>
          <p>
            Your application should support session management; at
            a minimum, it should save and restore the currently
            open documents.
          </p>
        </li>
        <li>
          <p>
            If appropriate, use the <tt class="CLASSNAME">
            GnomeApp</tt> for your main document windows; this
            widget gives Gnome applications a consistent
            look-and-feel.
          </p>
        </li>
        <li>
          <p>
            Call <tt class="FUNCTION">gtk_window_set_wmclass()</tt>
            to set the class hint on your windows, so users can
            customize how window managers treat them.
          </p>
        </li>
        <li>
          <p>
            Use <span class="STRUCTNAME">GnomeUIInfo</span> to
            create menus and toolbars; when appropriate, use the
            Gnome macros for standard menu items.
          </p>
        </li>
        <li>
          <p>
            Add a status bar to display hints for the menu items,
            and any other status your application has to report.
          </p>
        </li>
        <li>
          <p>
            Use <tt class="CLASSNAME">GnomeDialog</tt> and its
            subclasses for your dialogs.
          </p>
        </li>
        <li>
          <p>
            Add online help, including tooltips and documentation
            for display in the help browser.
          </p>
        </li>
        <li>
          <p>
            Keep a <tt class="FILENAME">ChangeLog</tt> detailing
            changes to your source code. This will help other
            people understand the evolution of the application, and
            help you understand why you made certain changes years
            later.
          </p>
        </li>
      </ul>
    </div>
    <div class="NAVFOOTER">
      <br>
      <br>
      <table width="100%" border="0" bgcolor="#ffffff" cellpadding= 
      "1" cellspacing="0">
        <tr>
          <td width="25%" bgcolor="#ffffff" align="left">
            <a href="sec-dialogs-convenience.html"><font color= 
            "#0000ff" size="2"><b>&lt;&lt;&lt;
            Previous</b></font></a>
          </td>
          <td width="25%" colspan="2" bgcolor="#ffffff" align= 
          "center">
            <font color="#0000ff" size="2"><b><a href="ggad.html">
            <font color="#0000ff" size="2"><b>
            Home</b></font></a></b></font>
          </td>
          <td width="25%" bgcolor="#ffffff" align="right">
            <a href="advanced.html"><font color="#0000ff" size="2">
            <b>Next &gt;&gt;&gt;</b></font></a>
          </td>
        </tr>
        <tr>
          <td colspan="2" align="left">
            <font color="#000000" size="2"><b>Convenience
            Routines</b></font>
          </td>
          <td colspan="2" align="right">
            <font color="#000000" size="2"><b>Advanced GTK+/Gnome
            Techniques</b></font>
          </td>
        </tr>
      </table>
    </div>
  </body>
</html>