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

List:       kde-frameworks-devel
Subject:    Re: T13975: Move hanyoung/libkweather to frameworks/kweathercore
From:       David Edmundson <david () davidedmundson ! co ! uk>
Date:       2020-12-20 14:25:36
Message-ID: CAGeFrHAvF0AUJ6BDK9yurAgDo3SJ383jpX839aS4Qs7yC=bTrA () mail ! gmail ! com
[Download RAW message or body]

On Sun, 20 Dec 2020, 11:48 Friedrich W. H. Kossebau, <kossebau@kde.org>
wrote:

> (Added Han Young as BCC: based on code email address, as the task is not
> public, and not sure you are subscribed to the mailinglists)
>
> Am Sonntag, 20. Dezember 2020, 12:05:46 CET schrieb David Edmundson:
> > Please see https://community.kde.org/Policies/Application_Lifecycle
> about
> > the process of adding things to frameworks.
> >
> > As for plasma, we have a weather library there, so the comment about it
> > being easier for new plasmoids doesn't hold directly. Maybe you can
> expand
> > on what's different?
>
> David, any chance you misremembered there being a weather library? If you
> refer to the stuff in plasma-workspace (which then e.g. drives the kde-
> plasmaaddons weather applet), that is just a DataEngine.
>

That is what I was referring to, yes.
It may be "just" a dataengine, but the end-result of plasmoids/apps being
able to get weather data is the same.

I also have no qualms about replacing it for the same reasons you outlined
(except maybe that this has a very hardcoded single backend), but we want
to make sure we don't end up with two things.

David

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Sun, 20 Dec 2020, 11:48 Friedrich W. H. Kossebau, &lt;<a \
href="mailto:kossebau@kde.org" target="_blank">kossebau@kde.org</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">(Added Han Young as BCC: based on \
code email address, as the task is not <br> public, and not sure you are subscribed \
to the mailinglists)<br> <br>
Am Sonntag, 20. Dezember 2020, 12:05:46 CET schrieb David Edmundson:<br>
&gt; Please see <a href="https://community.kde.org/Policies/Application_Lifecycle" \
rel="noreferrer noreferrer" \
target="_blank">https://community.kde.org/Policies/Application_Lifecycle</a> \
about<br> &gt; the process of adding things to frameworks.<br>
&gt; <br>
&gt; As for plasma, we have a weather library there, so the comment about it<br>
&gt; being easier for new plasmoids doesn&#39;t hold directly. Maybe you can \
expand<br> &gt; on what&#39;s different?<br>
<br>
David, any chance you misremembered there being a weather library? If you <br>
refer to the stuff in plasma-workspace (which then e.g. drives the kde-<br>
plasmaaddons weather applet), that is just a \
DataEngine.<br></blockquote></div></div><div dir="auto"><br></div><div \
dir="auto">That is what I was referring to, yes.<br></div><div>It may be \
&quot;just&quot; a dataengine, but the end-result of plasmoids/apps being able to get \
weather data is the same.<br></div><div><br></div><div>I also have no qualms about \
replacing it for the same reasons you outlined (except maybe that this has a very \
hardcoded single backend), but we want to make sure we don&#39;t end up with two \
things.<br></div><div dir="auto"><br></div><div dir="auto">David</div></div> </div>



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