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
|
<HTML>
<HEAD>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Control-center specs</TITLE>
<META NAME="GENERATOR" CONTENT="emacs rulez">
<META NAME="AUTHOR" CONTENT="dam's">
</HEAD>
<BODY>
<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
<TR>
<TD>
Control center group specs
</TD>
<TD>
12/19/00
</TD>
</TR>
<TR>
<TD>
Note : The previous document is adapted from <A
HREF=http://intranet.mandrakesoft.com/products/works-8.0/controlcenter.html>http://intranet.mandrakesoft.com/products/works-8.0/controlcenter.html</A>
which was ugly.
</TD>
</TR>
</TABLE>
<H1>Specifications</H1>
<H2>Introduction</H2>
<ul>
<li>The goal is to replace <B>DrakConf</B>with a unified interface for all components. <br>
An interface like HelixCode / Eazel is the goal, which may need to be
customized with a MandrakeSoft Look and Feel.
To achieve this we will extend gtk+mdk to include wizards, default sets
for menus, for icons,...
Each component will have to be usable either as a component or embedded in
the Linux-Mandrake Control Center
Front and back ends will be separated as much as possible for several
reasons:<br>
<ul>
<li>have the ability to write different interfaces (text, gtk*, web, ...)
according to the product</li>
<li>have more flexibility to modify rapidly the interfaces</li>
</li>
<li>
</ul>
DrakConf will still exist. But the number of item will be reduced. The tools
will be grouped in 6 groups, described here. Here is a screenshot of what it
could be. Some work is still neede to clearly define what will be the look of
this DrakConf. Question : do we want to keep its name 'DrakConf'?
Here is a first screenshot : <br>
<A HREF=screenshot1.png> futur of DrakConf </A>
</li>
<li>
Each group will launch a new window with configurations tools called here
'control window'. Here are some
screenshots of what this window will be : <br>
<A HREF=screenshot2.png> screenshot a </A> <br> <A HREF=screenshot3.png> screenshot b </A>
</li>
<li>Having a newbie and an expert mode for this tools would be useful.</li>
<li>Having a wizard mode for this tools would be required for some of them, and
useful for the others.</li>
</ul>
<H2>Groups descriptions</H2>
Note : every names are here for reference, The names will be replaced by their
functions, like before (ex: 'startup services' instead of drakexservices)
<H3>Menu customization</H3>
<ul>
<li> <H2>Content</H2>
<ul> <li><B>menudrake</B></li>
</ul>
<li>This group will just launch <B>menudrake</B> without control window.
</li>
<li>The idea is to transfer the existing <B>menudrake</B> application to the
new Control center. Details are given in the Desktop project.
</li>
</ul>
<H3>Boot Configuration</H3>
<UL>
<li> <H2>Content</H2>
<ul> <li><B>drakboot</B> </li>
<li> <B>drakfloppy</B> </li>
<li> <B>drakelogo</B> </li>
<li> <B>drakxservices</B> </li>
<li> <B>a new tool</B> to enable/disable the graphical boot </li>
</ul>
<li> <H2>Additional improvements </H2>
<ul> <li>Adapt <B>drakboot</B> to the new model to easily edit the entries of the
boot loader. </li>
<li> : <B>drakexservices</B>
This tool should also be part of the Boot configuration tool. It replaces
the current <B>drakxservices</B> with an interface similar to the
service tool on Windows NT, as shown in the picture below.
Each service needs to be documented, so that the user can understand what
it does. <A HREF="services.png"> The screenshot.</A></li>
<li>New tool : Integrate a simple check-box that enable or disables the graphical boot, which
give the choice to the user between classical boot or graphical <B>Aurora</B> boot.<br> Purge
/tmp at each reboot + other options that come from the install 'miscellaneous' step</li>
</ul>
</ul>
<H3>Font Management</H3>
<ul>
<li> <H2>Content</H2>
<ul> <li><B>drakfont</B> </li>
</ul>
<li>Just
adapt the current <B>drakfont</B> program to the new interface
guidelines.</li>
</ul>
<H2>Network and Internet Connection</H2>
<UL>
<li> <H2>Content</H2>
<ul> <li><B>draknet</B> </li>
<li> <B>drakgw</B> </li>
<li> <B>new tool : </B>firewall conf </li>
</ul>
<li> <H2>Additional improvements </H2>
<ul> <li> Adapt <B>drakprofile</B> to be
able to select a network profile at boot time (related to <B>draknet</B>)</li>
<li>Adapt
existing <B>draknet</B> and <B>drakgw</B> to use the wizard user
interface (see interface guideline document)</li>
<li>Separate
as discussed front-end and back-end to isolate the administration part.</li>
<li>Minimal firewall : firewall configuration tool.
This tool is described in the Security project.</li>
</UL>
</ul>
<H2>Hardware configuration</H2>
<ul>
<li> <H2>Content</H2>
<ul> <li><B>XFDrake</B> </li>
<li> <B>mousedrake</B> </li>
<li> <B>printerdrake</B> </li>
<li> <B>keyboarddrake</B> </li>
</ul>
<li> <H2>Additional improvements </H2>
<ul>
<li> IMHO, a merge of all hardware related configuration tool in a harddrake like
application is not possible for the deadline, so this need to be discuss, but
by default, I remove it from here. </li>
<li> Decisions about harddrake an its integrations are opened. </li>
</ul>
</ul>
<H2>Users and groups management</H2>
<ul>
<li> <H2>Content</H2>
<ul> <li><B>userdrake</B> </li>
</ul>
<li> <H2>Additional improvements </H2>
<li>Port the current <B>userdrake</B> in
the Control Center, with the following functions to add:
<UL>
<LI>Delete user & Archive /home/$user folder</li>
<LI>Add user specific properties (like menus)</li>
</UL> </li>
<ul>
</ul>
</ul>
<br>
<H1 STYLE="page-break-before: always">Development schedule</H1>
<P><I>Schedule format to be
defined later. </I></p>
<H1>Development Notes</H1>
<P>Free format text. Used by
developers to keep track of important issues.</p>
<P><I>First issue is detailed
snapshots with comments for all components, to be added here.</I></P>
<br>
<H1>Validation and Test Plan</H1>
<P<I>Define
the specific test to be performed</P>
<UL>
<LI><I>by
the development team</i>
<LI><I>by QA</I></P>
</UL>
<P><I>List Use case scenarios, and other test related reference documents</I></P>
<br>
<H1>Product Release</H1>
<P><I>Used to sign off project.</I></P>
</BODY>
</HTML>
|
