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

List:       kde-usability
Subject:    Re: A suggestion
From:       "Jos Poortvliet" <jos () mijnkamer ! nl>
Date:       2007-03-01 12:41:52
Message-ID: 5c77e14b0703010441s1e1c6bb4sd7a41d9e1ede8b14 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 3/1/07, Ben Aceler <aceler@gmail.com> wrote:
>
> Most of the linux distro have its own configuration tools like DrakConf,
> YaST
> and so on. Why not make a standard plug-in API for the KDE control center
> for
> all of this configuration utilities with one authentication mechaninsm?

What exactly do you mean? Should WE (eg KDE) integrate these apps in
Kcontrol, or should we provide an API for these to integrate in Kcontrol?
The latter more or less already exists, and YaST already does integrate in
Kcontrol... Guidance, the configuration tools for Kubuntu also could be
integrated in Kcontrol (and ARE integrated in Kubuntu's kcontrol replacement
'system settings').

Have a look at ksmshell, you can easilly create your own kcontrol
replacement. Using kparts etcetera makes building a ksm module for settings
easy, and I guess distributions could do that (Suse did). They just don't
want to.


--
> mailto://aceler@gmail.com
> jabber://aceler@jabber.ru
> http://aceler.livejournal.com/
> _______________________________________________
> kde-usability mailing list
> kde-usability@kde.org
> https://mail.kde.org/mailman/listinfo/kde-usability
>

[Attachment #5 (text/html)]

<br><br><div><span class="gmail_quote">On 3/1/07, <b class="gmail_sendername">Ben \
Aceler</b> &lt;<a href="mailto:aceler@gmail.com">aceler@gmail.com</a>&gt; \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Most of the linux distro \
have its own configuration tools like DrakConf, YaST<br>and so on. Why not make a \
standard plug-in API for the KDE control center for<br>all of this configuration \
utilities with one authentication mechaninsm? </blockquote><div>What exactly do you \
mean? Should WE (eg KDE) integrate these apps in Kcontrol, or should we provide an \
API for these to integrate in Kcontrol? The latter more or less already exists, and \
YaST already does integrate in Kcontrol... Guidance, the configuration tools for \
Kubuntu also could be integrated in Kcontrol (and ARE integrated in Kubuntu&#39;s \
kcontrol replacement &#39;system settings&#39;). <br><br>Have a look at ksmshell, you \
can easilly create your own kcontrol replacement. Using kparts etcetera makes \
building a ksm module for settings easy, and I guess distributions could do that \
(Suse did). They just don&#39;t want to. <br>&nbsp;</div><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;">--<br><a \
href="mailto:mailto://aceler@gmail.com">mailto://aceler@gmail.com</a> <br><a \
href="mailto:jabber://aceler@jabber.ru">jabber://aceler@jabber.ru</a><br><a \
href="http://aceler.livejournal.com/">http://aceler.livejournal.com/</a><br>_______________________________________________<br>kde-usability \
mailing list <br><a href="mailto:kde-usability@kde.org">kde-usability@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/kde-usability">https://mail.kde.org/mailman/listinfo/kde-usability</a><br></blockquote></div><br>




_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability


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