any issue (I strongly doubt
it), it definitely makes sense to me.
- Dario Freddi
On Jan. 12, 2016, 9:36 a.m., Martin Gräßlin wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboa
2015-11-19 17:17 GMT+01:00 René J.V. :
> On Thursday November 19 2015 15:21:10 Dario Freddi wrote:
>
>> * KIdleTime strives to be as lightweight as possible. This is something
>>which came from the old approach used in KDE3/4 powermanagement which was
> ...
>>resource
Given I already stepped in...
2015-11-19 10:36 GMT+01:00 René J.V. :
>
> Now it's just bad code, eh?
>
> Just for the record: no one but Apple really knows what IOKit considers being
> idle but it clearly involves absence of user input events. That's "user
> idle", not "system idle" (term from t
Hi René,
just thought I'd clarify some things as the creator/former maintainer of
all this - which might also justify some of Martin's positions.
The idea behind KIdleTime is that the framework shall be a lightweight,
non-critical framework for those applications which want to know about the
idle
---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/113851/
> ---
>
> (Updated Nov. 15, 2013, 8:38 a.m.)
>
>
> Review request for KDE Frameworks and Dario Freddi.
&g
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113851/#review43705
---
Ship it!
Ship It!
- Dario Freddi
On Nov. 15, 2013, 8:38
2012/9/21 Mark :
> On Tue, Sep 18, 2012 at 12:17 AM, Dario Freddi wrote:
>> (putting back plasma-devel on CC, since the discussion is quite relevant)
>>
>> 2012/9/17 Sune Vuorela :
>>>> I know Sune already had some plans for the notification stack and I
>>&g
2012/9/21 Aaron J. Seigo :
> if the "new" can be achieved by extending or building on galago, that would
> seem to me to be a much better thing.
>
> and no, galago is not perfect. it's not even "great", but it is passable and
> widely used and that gives it a lot of value.
>
> if it turns out that
2012/9/20 Sune Vuorela :
> On 2012-09-17, Dario Freddi wrote:
>> It really depends on what you want to achieve. If your goal is just
>> cleaning up the API and implementing the existing standard it might
>> work out, but for sure it won't just cut it for what I propose
(readded frameworks, the topic ping-pongs)
2012/9/18 Aaron J. Seigo :
> On Monday, September 17, 2012 20:40:33 Dario Freddi wrote:
>> it's pretty much on the board :) just that 90% of this will happen in
>> the background (server), whereas handlers will just take care of
>
(putting back plasma-devel on CC, since the discussion is quite relevant)
2012/9/17 Sune Vuorela :
>> I know Sune already had some plans for the notification stack and I
>> think that's one of the best times for discussing what's going to
>
> yep. the plan is
> 1) write a small library wrapping th
2012/9/17 David Faure :
> On Monday 17 September 2012 17:49:23 Dario Freddi wrote:
>> a server API (so that the
>> server can be put into runtime rather easily)
>
> Just a note on that: the plan with KDE Frameworks, is that there will be no
> more libs/runtime separatio
Hello everyone,
you might or might not know by now of my intention of revamping the
way we deal with notifications in KDE as I explained in my last blog
post
http://drfav.wordpress.com/2012/09/17/the-notifications-issue-part-3-the-possible-solution/
. I have been talking about this with many of y
2012/8/31 Kevin Ottens :
> Now if that was a case of "the framework can't work without the dependency"
> I'd have a position similar to your. But here it's depending on the nature of
> the plugins, not on what the framework itself needs, that's what rings the
> "worth doing it" to me.
I understand
2012/8/31 Kevin Ottens :
> Hello,
>
> On Wednesday 29 August 2012 23:53:32 David Faure wrote:
>> KService, KServiceTypeTrader and KMimeTypeTrader (all of which I moved to a
>> new "kservice" framework), all have a template method (createInstance*)
>> which uses KPluginLoader to load the plugin desc
2012/5/6 Stephen Kelly :
> Kevin Ottens wrote:
>
>> * kidletime, the only one not started, somewhat independent though, Dario
>> is the maintainer.
>
> I notice that this one uses a lot of X11.
>
> Is porting from xlib to xcb part of considering something like this 'done'?
> KWindowSystem still use
Il 20 marzo 2012 17:53, Kevin Ottens ha scritto:
> On Sunday 18 March 2012 20:11:20 Kevin Ottens wrote:
>> So, doable? Any volunteers (aha) to drive the volunteer day? :-)
>
> Dario indicated to me he could be available part of the afternoon, that's nice
> but likely not enough.
Screw this GMail,
For interested people (hopefully many)
-- Messaggio inoltrato --
Da: Dario Freddi
Date: 18 marzo 2012 23:25
Oggetto: Review Request: Make KAuth ready for frameworks + API Changes
A: Kevin Ottens , David Faure , Alexander
Neundorf
Cc: Dario Freddi , kdelibs , Dario
Freddi
Hi,
2012/3/1 Frank Reininghaus :
> Hi,
>
> Am 1. März 2012 00:44 schrieb Dario Freddi:
>> I was wondering if we already had a way to generate reports on
>> autotests coverage using lcov/gcov in frameworks. Looking at our cmake
>> infrastructure, I spotted a build
Hey guys,
I was wondering if we already had a way to generate reports on
autotests coverage using lcov/gcov in frameworks. Looking at our cmake
infrastructure, I spotted a build mode "Profile" which should
apparently set the correct compiler flags (but actually, at least for
me, it didn't work), I
2012/2/19 Ben Cooksley :
>
> First, our hooks are in python - so any changes would need to be in Python
> as well.
I can speak a bit of python, would be a nice way for learning more :)
>
> Second, there is a legitimate use for pushing merge commits - namely
> integrating a seperate remote branch.
2012/2/19 Stephen Kelly :
> Stephen Kelly wrote:
>
>>
>> Hi there,
>>
>> I was reviewing the changes in the frameworks branch from yesterday.
>> Something I noticed was that there are a lot of merge commits that don't
>> need to exist.
>
> Ugh. Yet more of this just appeared... Recent history in th
2012/1/31 David Faure :
> On Thursday 26 January 2012 16:12:22 Dario Freddi wrote:
>> Forwarding to framework, hoping somebody here cares...
>
> I don't see the relation. I could answer all these questions for kdelibs, but
> your question is about kde-workspace, which isn&#
Forwarding to framework, hoping somebody here cares...
-- Forwarded message --
From: Dario Freddi
Date: 2012/1/20
Subject: Forward porting policy
To: kde-core-de...@kde.org
Howdy,
I just pushed a fix to KDE/4.8 in workspace. Now, when trying to
forward-port as usual, a
2011/12/6 Kevin Ottens :
> On Tuesday 06 December 2011 18:45:38 Dario Freddi wrote:
>> Hello everyone,
>>
>> I know some of you are crying blood just by looking at the title, but
>> yes, I want to bring this up :)
>>
>> I think Frameworks could be a good chan
2011/12/6 George Kiagiadakis :
> On Tue, Dec 6, 2011 at 10:54 AM, Aaron J. Seigo wrote:
>> On Monday, December 5, 2011 12:23:30 Chusslove Illich wrote:
>>> Regarding yesterday's chat, to shortly (really!) sum up my stance on i18n.
>>>
>>> 1) I see no point at striving for single translation system
Hello,
I am in process of porting some components to the new Frameworks
structure. Following
http://community.kde.org/Frameworks/Strategy_and_Policies#Framework_directory_structure,
I noticed there are still some gaps. KAuth, for example, has a
ConfigureChecks.cmake file. Now, for some reasons I m
Hello everyone,
I know some of you are crying blood just by looking at the title, but
yes, I want to bring this up :)
I think Frameworks could be a good chance to enhance and force
requirements regarding unit tests, especially for new code. I am the
first who apologizes as most of the code I comm
2011/12/5 Aaron J. Seigo :
> hi..
>
> the Plasma team is working on the kactivities repository with the idea in mind
> that it is a "frameworks 5" style project right from the start.
>
> it currently contains a library (libkactivities), a runtime componen
> (kactivitymanagerd) and some runtime data
29 matches
Mail list logo
