[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 18:08:12
Message-ID: k2h757d9a551004291108m7a745d1ajb6e0a0c258cdbce0 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Apr 29, 2010 at 6:04 PM, Aaron J. Seigo <aseigo@kde.org> wrote:
> On April 29, 2010, Aleix Pol wrote:
> > plasma-desktop-appletsrc) so that we can use the project file to store
> such
> > information (it's important to specify our own because we want that to be
> > versioned with the project).
>
> can it be a file inside the project, or does it have to be the project file
> itself?
>
> this will also likely require some small changes in libplasma, as Corona
> has a
> variable for the config file to use, but it's only set internally based on
> whether there is a main component or not.
>
> --
> 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.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
Does it make a difference?
That's why I said it would be nice to provide the KConfig instance that we
want Plasma to use.
It would be nice to have everything on the same file. If it's not possible I
could workaround that in the KDevelop side probably...
[Attachment #5 (text/html)]
<div class="gmail_quote">On Thu, Apr 29, 2010 at 6:04 PM, Aaron J. Seigo <span \
dir="ltr"><<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>></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> > plasma-desktop-appletsrc) so that we can \
use the project file to store such<br> > information (it's important to \
specify our own because we want that to be<br> > versioned with the project).<br>
<br>
</div>can it be a file inside the project, or does it have to be the project file<br>
itself?<br>
<br>
this will also likely require some small changes in libplasma, as Corona has a<br>
variable for the config file to use, but it's only set internally based on<br>
whether there is a main component or not.<br>
<br>
--<br>
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><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</blockquote></div><br>Does it make a difference?<br>That's why I said it would \
be nice to provide the KConfig instance that we want Plasma to use.<br><br>It would \
be nice to have everything on the same file. If it's not possible I could \
workaround that in the KDevelop side probably...<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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic