[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC: Changes to KControl for KDE 3.0
From:       Dirk Mueller <mueller () kde ! org>
Date:       2001-09-05 18:58:10
[Download RAW message or body]

On Mit, 05 Sep 2001, Daniel Molkentin wrote:

> All modules should be called kcm<modulename>, for example the modules to set 
> up the font module should be called "kcmfonts" instead of simply "fonts". The 
> current way (mixing up both) is extremely confusing. The directory holding 
> the config module should always be called kcm<modulename>. Otherwise we might 
> end up in situations like the "display" directory which holds the "style" 
> module.

are you talking about directory names in CVS or about the installed 
directory structure ?

> 2. Reorganization of  the directory structure: 
> All modules should be hosted in a subdirectory of the according main 
> application. However, I see that there are cases where modules span across 
> multiple applications or are system-wide settings in which case we could 
> still put them under kcontrol/ (I'd even prefer another subdir like 
> "generic").

Why ? whats the advantage ?


Dirk

[prev in list] [next in list] [prev in thread] [next in thread]