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
|
<chapter id="introduction">
<chapterinfo>
<releaseinfo>$Progeny: introduction.xml,v 1.7 2002/01/18 06:19:44 dsp Exp $</releaseinfo>
</chapterinfo>
<title>Introduction</title>
<section id="sec-intro-overview">
<title>Overview</title>
<para>
The &debconf; system, while very useful, is forced by design to
provide a <emphasis>least common denominator</emphasis> approach to
its user interface. While this is very useful for accomodating the
many environments that a package might be configured, it does make
&debconf; interfaces in richer environments look ugly and difficult
to use by comparison.
</para>
<para>
<emphasis>Configlets</emphasis> supply an architecture to support
richer front ends that can leverage advanced environments such as
&gnome;. Developers can create Python code and a Glade interface to
be presented to the user by a separate front end; behind the scenes,
&debconf; is used to store questions and answers for future use,
just as it would otherwise.
</para>
<para>
The current &gnome; front ends include a druid to invoke each
configlet as a wizard, and individual capplets that are
incorporated into the &gnome; control center.
</para>
<itemizedlist>
<title>Debian packages</title>
<listitem>
<para><application>python-configlets</application> contains the
core infrastructure.</para>
</listitem>
<listitem>
<para><application>configlet-frontends</application>
provides the &gnome; druid front end and capplet interface.
</para>
</listitem>
</itemizedlist>
</section>
</chapter>
<!-- Local variables: -->
<!-- eval: (sgml-load-dtd "../../doctools/docbook.ced") -->
<!-- End: -->
|
