Differences between revisions 2 and 3
Revision 2 as of 2004-08-18 21:59:24
Size: 1141
Editor: anonymous
Comment:
Revision 3 as of 2004-08-18 22:46:34
Size: 2765
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
=== Abbreviation of Debian Control Center: dcontrol === ----
Line 5: Line 5:
One of the biggest problems with new/desktop users of Linux is their capacity to configure a system, how to deal with proper stuff to have a installation working soon. Debian, being a distribution with high quality assurance standards and being completely free, let users freedom of usage, but probably a not very intuitive way to set it up. Because of the absence of a proper tool to do this, dcontrol project aims to fit this needs. One of the biggest problems with new/desktop users of Linux is their capacity to configure a system, how to deal with proper stuff to have a installation working soon. Debian, being a distribution with high quality assurance standards and being completely free, let users freedom of usage, but probably a not very intuitive way to set it up. Because of the absence of a proper tool to do this, ''dcontrol'' project aims to fit this needs.
Line 11: Line 11:
== Aims of dcontrol ==
 * dcontrol will be available in four ports:
''dcontrol'' will use debconf as backend for configuration and implement its own parsers for anything not yet debconfinizated.

== dcontrol thoughts ==
 * Main ideas were thrown on the IRC meeting: http://www.damog.net/debian/debian-control-center.log
 * ''dcontrol'' will be available in probably five ports:
Line 15: Line 18:
   * Java port.
Line 17: Line 21:
 * Hack gnome-system-backends to be able to talk with debconf from any toolkit or language.
 * ''dcontrol'' will be able to perform configuration for normal user as well as system user.
 * ''dcontrol'' should be able to share virtual configurations, a common configuration for any kind of service.
 * ''dcontrol'' could be able to configure desktop preferences for any kind of desktop/wm and be able to share it between them.
 * ''dcontrol'' could be able to speak with other d-bus desktop applications, in order to retrieve relevant information to use it as User Preferences.
 * ''dcontrol'' should be able to work and set mount points up automagically, using desktop autofs.
 * ''dcontrol'' may be able to handle removable media access over an X extension
 * ''dcontrol'' will be able to set runlevels up with gnome-system-tools or rcconf
 * '''''debconf''''' will be the tool used to interact with the Debian system.
Line 18: Line 31:
---- == dcontrol suggestions ==
 * configlets should be hacked to use it as frontend.

== How can I help? ==
 * First, thanks ;-)
 * Writing your suggestions on this wiki.
 * Right now code work is appreciate it in any port.
 * Studying debconf as the main backend.
 * Helping cordinating this mess.
 * Joining debian-desktop mailing list and help with the subproject.
 * With graphic design and art.

== What's next? ==
An Alioth project will be created, please refer to it, as soon as it gets active.

Debian Control Center


What is Debian Control Center?

One of the biggest problems with new/desktop users of Linux is their capacity to configure a system, how to deal with proper stuff to have a installation working soon. Debian, being a distribution with high quality assurance standards and being completely free, let users freedom of usage, but probably a not very intuitive way to set it up. Because of the absence of a proper tool to do this, dcontrol project aims to fit this needs.

We need to provide good graphical user interface for configuration of already existing debconf infrastructure and use debconf where possible, only providing special code to configure stuff where debconfization is not possible.

The reason to create one from the scratch is to set up a complete native system with Debian, developed by and for Debian community.

dcontrol will use debconf as backend for configuration and implement its own parsers for anything not yet debconfinizated.

dcontrol thoughts

  • Main ideas were thrown on the IRC meeting: http://www.damog.net/debian/debian-control-center.log

  • dcontrol will be available in probably five ports:

    • GTK+ port.
    • Qt port.
    • Java port.
    • CLI (written in C/C++) port.
    • Web-based (written in Perl) port.
  • Hack gnome-system-backends to be able to talk with debconf from any toolkit or language.
  • dcontrol will be able to perform configuration for normal user as well as system user.

  • dcontrol should be able to share virtual configurations, a common configuration for any kind of service.

  • dcontrol could be able to configure desktop preferences for any kind of desktop/wm and be able to share it between them.

  • dcontrol could be able to speak with other d-bus desktop applications, in order to retrieve relevant information to use it as User Preferences.

  • dcontrol should be able to work and set mount points up automagically, using desktop autofs.

  • dcontrol may be able to handle removable media access over an X extension

  • dcontrol will be able to set runlevels up with gnome-system-tools or rcconf

  • debconf will be the tool used to interact with the Debian system.

dcontrol suggestions

  • configlets should be hacked to use it as frontend.

How can I help?

  • First, thanks ;-)

  • Writing your suggestions on this wiki.
  • Right now code work is appreciate it in any port.
  • Studying debconf as the main backend.
  • Helping cordinating this mess.
  • Joining debian-desktop mailing list and help with the subproject.
  • With graphic design and art.

What's next?

An Alioth project will be created, please refer to it, as soon as it gets active.