On Sunday 27 March 2011 23:54:02 José Expósito wrote:
> > as separate ded? (so something new, generic in kde-workspace)
>
> I'm sorry, I don't know if I understand you well (ded?).
He meant kded.
The generic way of creating small daemons in KDE workspace is doing it as a
"KDED Module". A kded ba
hello,
which is the difference between the two above?
And actually in general what i gain/lose if i use a debug area?
thanks in advance
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Sun, Mar 27, 2011 at 14:54, José Expósito wrote:
>> as separate ded? (so something new, generic in kde-workspace)
I think he meant "kded"
- Jeffery MacEachern
> I'm sorry, I don't know if I understand you well (ded?).
>
> I think that a separate daemon could be the better opcion, because
> p
> as separate ded? (so something new, generic in kde-workspace)
I'm sorry, I don't know if I understand you well (ded?).
I think that a separate daemon could be the better opcion, because
people without trackpad or touchscreen could disable it and because,
as far as I know, KDE haven't got any si
Hi,
On 03/27/11 21:24, Marco Martin wrote:
> to me, as i explained before what is important is not much the applications
> per se, but how are written and how they use said mobile stack, i'm still not
> sure how many of those pieces should be plasmoids, how many separate
> applications
> 99% o
On Sunday 27 March 2011, Davide Bettio wrote:
> Hi,
>
> This mail is about two topics: gsoc and mobile.
> Firstly, I am going to explain to you what I've been doing recently and
> what goals I have reached.
> I've started to work on the mobile stack since I've written a QML demo
> application call
Hi,
This mail is about two topics: gsoc and mobile.
Firstly, I am going to explain to you what I've been doing recently and
what goals I have reached.
I've started to work on the mobile stack since I've written a QML demo
application called "mobile dolphin", since that day I've been working on
sev
On Sun, Mar 27, 2011 at 10:40 AM, Marco Martin wrote:
> On Sunday 27 March 2011, José Expósito wrote:
>> Yes, I'm totally agree Kwin is not the place to this code, and of
>> course it works with any WM, I only suggest it in this list because
>> I'm really interested in work this summer in Kwin.
>>
On Sunday 27 March 2011, José Expósito wrote:
> > I see three things which speak against having it in KWin:
> > [...]
>
> Yes, I'm totally agree Kwin is not the place to this code, and of
> course it works with any WM, I only suggest it in this list because
> I'm really interested in work this su
Hello,
> to me multitouch support means basically two possible things (just as local vs
> global shortcuts)
> for the secons case qt api is pretty much enough to easily use gestures in any
> app.
> for the first case some system wide daemon should filter gestures and manage
> the one that it suppo
On Sunday 27 March 2011 11:45:01 Marco Martin wrote:
> it's also true that most of those gestures would be pretty window manager
> specific, so could even make sense in kwin..
I see three things which speak against having it in KWin:
1. There are valid global functions independent of KWin. E.g. Sh
On Saturday 26 March 2011, José Expósito wrote:
> Hello Martin,
>
> > I think your multitouch work would be valuable for complete KDE.
> >
> > In my opinion it's not something that needs to be in KWin, but might be
> > better as a KDED module available to the complete workspace. That's why
> > I
12 matches
Mail list logo
