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

List:       kde-panel-devel
Subject:    Re: using plasma for KDevelop dashboard
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2010-04-29 23:07:07
Message-ID: m2u757d9a551004291607tc5be863er7eaf555e06bc947f () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, Apr 29, 2010 at 8:51 PM, Aaron J. Seigo <aseigo@kde.org> wrote:

> On April 29, 2010, Aleix Pol wrote:
> > Does it make a difference?
>
> not so much from the libplasma side. but sharing config files is a great
> way
> to lead to unexpected naming collisions. if avoidable, that would be nice.
>
> if it isn't possible, then we probably want to look into being able to
> define
> the KConfigBase to use so that a KConfigGroup group can be passed in,
> giving
> some automatic scoping inside the config file and avoiding any possibility
> of
> naming collisions later on.
>
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
>
> KDE core developer sponsored by Qt Development Frameworks
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.orgI'
> https://mail.kde.org/mailman/listinfo/plasma-devel
>

Having a prefix would be great.
We can also enforce some prefix from the kdevelop side, this config files
usage right now is very limited now so I'm not much concerned of this
namespacing effect even if I understand the risk and I'd love to be able to
forget about it :). Actually, IIRC it's possible to have groups inside
groups in KConfig files so this would be another way to separe :).

Thanks!
Aleix

[Attachment #5 (text/html)]

<div class="gmail_quote">On Thu, Apr 29, 2010 at 8:51 PM, Aaron J. Seigo <span \
dir="ltr">&lt;<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; \
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On \
April 29, 2010, Aleix Pol wrote:<br> </div><div class="im">&gt; Does it make a \
difference?<br> <br>
</div>not so much from the libplasma side. but sharing config files is a great \
way<br> to lead to unexpected naming collisions. if avoidable, that would be \
nice.<br> <br>
if it isn&#39;t possible, then we probably want to look into being able to define<br>
the KConfigBase to use so that a KConfigGroup group can be passed in, giving<br>
some automatic scoping inside the config file and avoiding any possibility of<br>
naming collisions later on.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA   EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Development Frameworks<br>
_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a>I&#39;<br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</div></div></blockquote></div><br>Having a prefix would be great.<br> We can also \
enforce some prefix from the kdevelop side, this config files usage right now is very \
limited now so I&#39;m not much concerned of this namespacing effect even if I \
understand the risk and I&#39;d love to be able to forget about it :). Actually, IIRC \
it&#39;s possible to have groups inside groups in KConfig files so this would be \
another way to separe :).<br> <br>Thanks!<br>Aleix<br>



_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


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