Specifications

Introduction

• The goal is to replace DrakConfwith a unified interface for all components.
  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:
  
  • have the ability to write different interfaces (text, gtk*, web, ...) according to the product
  • have more flexibility to modify rapidly the interfaces
  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.
• screenshots of the global tool
  screenshot a
  screenshot b
• The tools that come from the install and have an expert mode are displayed with an 'expert mode button'.
• FIXEME: Draknet and drakegw will have a wizard mode. which other tools?.
• 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

Groups descriptions

Menu customization

• Content

  • menudrake
• menudrake in control window.
• The idea is to transfer the existing menudrake application to the new Control center. Details are given in the Desktop project.

Boot Configuration

• Content

  • drakboot
  • drakfloppy
  • drakelogo
  • drakxservices
  • a new tool to enable/disable the graphical boot

• Additional improvements

  • Adapt drakboot to the new model to easily edit the entries of the boot loader.
  • : drakexservices This tool should also be part of the Boot configuration tool. It replaces the current drakxservices with an interface as shown in the picture below. Each service needs to be documented, so that the user can understand what it does. The screenshot.
  • 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 Aurora boot.
    Purge /tmp at each reboot + other options that come from the install 'miscellaneous' step

Font Management

• Content

  • drakfont in the control center
• Just adapt the current drakfont program to the new interface guidelines.

Network and Internet Connection

• Content

  • drakconnect
  • drakgw
  • new tool : firewall conf

• Additional improvements

  • Adapt drakprofile to be able to select a network profile at boot time (related to drakconnect)
  • Adapt existing drakconnect and drakgw to use the wizard user interface (see interface guideline document)
  • Separate as discussed front-end and back-end to isolate the administration part.
  • Minimal firewall : firewall configuration tool. This tool is described in (and has to be provided by ) the Security project.

Hardware configuration

• Content

  • XFDrake
  • harddrake
  • mousedrake
  • printerdrake
  • keyboarddrake

• Additional improvements

  • A merge of all hardware related configuration tool in a harddrake like application is not possible for the deadline, so it's kept separated.

Users and groups management

• Content

  • userdrake

• Additional improvements

• Port the current userdrake in the Control Center, with the following functions to add:
  • Delete user & Archive /home/$user folder
  • Add user specific properties (like menus)
  • Add user language selection

Development schedule

Schedule format to be defined later.

Development Notes

Free format text. Used by developers to keep track of important issues.

First issue is detailed snapshots with comments for all components, to be added here.

Validation and Test Plan