<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>
<H1>Control center group specs</H1>
</TD>
<TD>
12/19/00
</TD>
</TR>
<TR>
<TD>
<H1>Team : Daouda, dindinx, dam's(leader)</H1>
</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>.
</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 is replaced by a gnomecc like interface.
Left, a tree, right, the applications. By default, an about page.
All applications can be launched in single mode or embedded.
</li>
<li>
screenshots of the global tool<br>
<A HREF=screenshot2.png> screenshot a </A> <br> <A HREF=screenshot3.png> screenshot b </A>
</li>
<li>The tools that come from the install and have an expert mode are displayed with an 'expert mode button'.</li>
<li>FIXEME: Draknet and drakegw will have a wizard mode. which other tools?. </li>
<li>In 8.0 UTF-8 locales will be available, and migration to UTF-8 will start.
Gtk+ toolkits seem to allow on the fly charset conversion of text used
by gettext in po files.
For other text we must mandate that they
be coded in UTF-8, and add the needed code to the application to convert
it to the user locale </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> <H4>Content</H4>
<ul> <li><B>menudrake</B></li>
</ul>
<li><B>menudrake</B> in 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> <H4>Content</H4>
<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> <H4>Additional improvements </H4>
<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 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> <H4>Content</H4>
<ul> <li><B>drakfont</B> in the control center </li>
</ul>
<li>Just
adapt the current <B>drakfont</B> program to the new interface
guidelines.</li>
</ul>
<H3>Network and Internet Connection</H3>
<UL>
<li> <H4>Content</H4>
<ul> <li><B>draknet</B> </li>
<li> <B>drakgw</B> </li>
<li> <B>new tool : </B>firewall conf </li>
</ul>
<li> <H4>Additional improvements </H4>
<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 (and has to be provided by ) the Security project.</li>
</UL>
</ul>
<H3>Hardware configuration</H3>
<ul>
<li> <H4>Content</H4>
<ul> <li><B>XFDrake</B> </li>
<li> <B>harddrake</B> </li>
<li> <B>mousedrake</B> </li>
<li> <B>printerdrake</B> </li>
<li> <B>keyboarddrake</B> </li>
</ul>
<li> <H4>Additional improvements </H4>
<ul>
<li> A merge of all hardware related configuration tool in a harddrake like
application is not possible for the deadline, so it's kept separated. </li>
</ul>
</ul>
<H3>Users and groups management</H3>
<ul>
<li> <H4>Content</H4>
<ul> <li><B>userdrake</B> </li>
</ul>
<li> <H4>Additional improvements </H4>
<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>
<LI>Add user language selection</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>