Differences between revisions 1 and 2
Revision 1 as of 2004-09-13 08:22:05
Size: 2677
Editor: anonymous
Comment:
Revision 2 as of 2004-09-13 11:21:29
Size: 2770
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 44: Line 44:
 * http://freedesktop.org/Software/CFG (use as backend and craft a really fine DCC frontend)

Debian Control Center Draft

User friendliness

  • DCC should provide te user with a central location for system configuration, this compromises both the users personal options and system wide defaults (or things that can only be configured for the system). The .desktop format described at freedesktop.org can be used to create a nice folder with links to all configuration tools. (Both kde & gnome support it)

  • The user should not be confronted with configuration files. DCC applications should leave comments and formatting intact.
  • User friendliness is the primary goal. Basic configuration is most important, advanced features can be (in a first stage) left unimplemented and should, if implemented, not be the first thing the user is confronted with (last tab/Expert button/...)
  • At regular times: put your father/mom/grandfather/grandmother/... in front of your computer and ask them to configure something. Sit back (relax?) and look at how the average user responds

About coding it

Some things you should allready know

  • The world is not expecting the next ugly cludge of code. Code should be organized in small modules, contain enough comments ... Some basic things most people expect of decent code.
  • Only use C(++) code when a) you're working on existing code that's the best out there b) no other option is available (feels assembler jokes coming..)
  • reuse
  • Insert some nice scripting languages here

/dev/random

Some random thoughts, eg. "this would be nice if..."

  • Network transparancy, eg. configure other computers localy - there are several ways of doing this, you could have the remote computer run something webmin-like or you could use the local applications to connect through < insert protocol > to a remote computer

  • Multiple interfaces: how accomplish multiple interfaces using the same code? You could write Yet Another Library for doing this... Haven't seen things that do html/gtk/qt/console...

Debconf would probably be able to do it, but is rather limited towards user interfaces (no placement/limited number of widgets/no true interaction...).

Something you can't do with debconf: user has one main box containing 3 choises, based on the choise the data presented below that box changes and presents options specific to the choice made by the user

Should we extend debconf, or keep looking for something else for ui abstraction?

What exists

A list of some applications/libraries/protocols that should be considered for inclusion/integration/usage