KDE/kdevplatform

[dukju ahn]

2007/7/15, Andreas Pakulat <apaku at gmx.de>:
> On 14.07.07 18:01:22, Dukju Ahn wrote:
> > SVN commit 687905 by dukjuahn:
> >
> > Fix the parent app name of envsetting kcm from kdevelop to kdevplatformproject.
> > Also, slight modification in projectCtrl to load kdevplatformproject kcm.
> >
> >
> >  M  +2 -2      project/settings/kcm_kdev_envsettings.desktop
> >  M  +3 -1      shell/projectcontroller.cpp
> >
> >
> > --- trunk/KDE/kdevplatform/project/settings/kcm_kdev_envsettings.desktop #687904:687905
> > @@ -7,8 +7,8 @@
> >  X-KDE-ModuleType=Library
> >  X-KDE-Library=kdev_envsettings
> >  X-KDE-FactoryName=kcm_kdev_envsettings
> > -X-KDE-ParentApp=kdevelop
> > -X-KDE-ParentComponents=kdevelop
> > +X-KDE-ParentApp=kdevplatformproject
> > +X-KDE-ParentComponents=kdevplatformprojecta
>
> This is not fully right. The parent app should be kdevplatform (see
> shell/settings/kcm_kdev_uisettings.desktop).

If we specify kdevplatform like uisetting, that kcm is loaded in
application global setting. Ui setting is global but project env
setting is per project.

That's just another name to avoide such confusion. Although
we introduce component name "kdevplatformproject", the actual
component data is not created. Only names are meaningful in
creating kcm dialog.