---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115162/#review47977
---
Ship it!
Please push this to a separate branch as Sinny sugge
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115162/
---
(Updated Jan. 22, 2014, 6:38 a.m.)
Review request for Plasma, Shantanu Tu
> On Jan. 21, 2014, 5:58 p.m., Shantanu Tushar wrote:
> > I couldn't try it right now but I have this doubt. If there is already a
> > PMC instance running and open a file from Dolphin, does the file indeed
> > start playing?
>
> Sujith Haridasan wrote:
> What I meant to say is if PMC is a
> On Jan. 21, 2014, 5:58 p.m., Shantanu Tushar wrote:
> > I couldn't try it right now but I have this doubt. If there is already a
> > PMC instance running and open a file from Dolphin, does the file indeed
> > start playing?
>
> Sujith Haridasan wrote:
> What I meant to say is if PMC is a
> On Jan. 21, 2014, 5:58 p.m., Shantanu Tushar wrote:
> > I couldn't try it right now but I have this doubt. If there is already a
> > PMC instance running and open a file from Dolphin, does the file indeed
> > start playing?
>
> Sujith Haridasan wrote:
> What I meant to say is if PMC is a
> On Jan. 21, 2014, 5:58 p.m., Shantanu Tushar wrote:
> > I couldn't try it right now but I have this doubt. If there is already a
> > PMC instance running and open a file from Dolphin, does the file indeed
> > start playing?
What I meant to say is if PMC is already running and if user tries t
Thanks, David for transferring the tasks.
On Tuesday, January 21, 2014 20:24:25 Marco Martin wrote:
> On Tuesday 21 January 2014 20:16:05 David Edmundson wrote:
> > Marco, Sebas - The proposed API changes were before my time in Plasma
> > and I assume are the result of a previous sprint. Frustrati
On Tuesday 21 January 2014 22:45:44 Kai Uwe Broulik wrote:
> Hi,
>
> +1 as well!
> Especially it popping up on session start where the compositor isn't fully
> ready. :/
>
> So to summarize:
> - never ever show it when the brightness changes automatically (session
> start, mouse movement, screen
Hi,
+1 as well!
Especially it popping up on session start where the compositor isn't fully
ready. :/
So to summarize:
- never ever show it when the brightness changes automatically (session start,
mouse movement, screen timeout, ...)
- if user changes, it show the OSD on the primary/internal mo
On Tue, Jan 21, 2014 at 10:00 PM, Thomas Pfeiffer wrote:
> On Saturday 18 January 2014 13:15:18 Martin Klapetek wrote:
>
> > > > Truth is you don't need to know the /exact/ brightness or volume
> level
> > > > in
> > > > fullscreen video, you simply fiddle with it until it suits you. In
> this
> >
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115027/
---
(Updated Jan. 21, 2014, 9:23 p.m.)
Status
--
This change has been ma
On Saturday 18 January 2014 13:15:18 Martin Klapetek wrote:
> > > Truth is you don't need to know the /exact/ brightness or volume level
> > > in
> > > fullscreen video, you simply fiddle with it until it suits you. In this
> > > case it's maybe not as much about showing the exact percentage, but
On Tuesday 21 January 2014 20:16:05 David Edmundson wrote:
>
> Marco, Sebas - The proposed API changes were before my time in Plasma
> and I assume are the result of a previous sprint. Frustratingly when I
> asked about one, I was told "I don't think we need to do that
> anymore". Could you look t
Awesome!
*Hugs*
David
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
During the sprint we made a list of the main items that block the next
plasma release.
Rather than starting a new list, I merged all information into the
existing wiki:
http://community.kde.org/Plasma/PW2Todo
PLEASE UPDATE THIS WIKI
There are a lot of existing tasks that I think are done which a
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115192/
---
Review request for kdewin and Plasma.
Repository: kdeplasma-addons
Desc
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115162/#review47915
---
I couldn't try it right now but I have this doubt. If there is
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115162/#review47913
---
Good work sujith! It works fine as expected.
Preferably, Someo
Hi there
In the Plasma sprint Martin Gräßlin and I sit down and check how many things
of kde-workspace beside KWin need work in order to run under Wayland.
Most of the work is quite easy to do some times just adding some #ifdef will
do the trick. The only areas that seem to require a special am
On Tue, Jan 21, 2014 at 3:28 PM, Martin Klapetek
wrote:
> On Tue, Jan 21, 2014 at 3:10 PM, Martin Gräßlin wrote:
>
>> On Tuesday 21 January 2014 14:26:59 Martin Klapetek wrote:
>> > On Tue, Jan 21, 2014 at 8:57 AM, Martin Gräßlin
>> wrote:
>> > > I had a look and the Plasma side seems fine. You c
On Tue, Jan 21, 2014 at 3:10 PM, Martin Gräßlin wrote:
> On Tuesday 21 January 2014 14:26:59 Martin Klapetek wrote:
> > On Tue, Jan 21, 2014 at 8:57 AM, Martin Gräßlin
> wrote:
> > > I had a look and the Plasma side seems fine. You can verify using
> xprop.
> > > My
> > >
> > > demo dialog got
On Tuesday 21 January 2014 14:26:59 Martin Klapetek wrote:
> On Tue, Jan 21, 2014 at 8:57 AM, Martin Gräßlin wrote:
> > I had a look and the Plasma side seems fine. You can verify using xprop.
> > My
> >
> > demo dialog got the notification type.
>
> Hmm...I might have been wrong then, using xp
On Tue, Jan 21, 2014 at 8:57 AM, Martin Gräßlin wrote:
> I had a look and the Plasma side seems fine. You can verify using xprop. My
> demo dialog got the notification type.
>
Hmm...I might have been wrong then, using xprop on the OSD I get
_NET_WM_WINDOW_TYPE(ATOM) = _KDE_NET_WM_WINDOW_TYPE_O
On Tuesday, January 21, 2014 11:03:57 Bhushan Shah wrote:
> On Tue, Jan 21, 2014 at 1:19 AM, Àlex Fiestas wrote:
> > In the plasma sprint we have done a session to plan what we are going to
> > do
> > with kde-workspace/kde-runtime repositories, here is the proposal we came
> > with.
> >
> > We a
Hello!
On Tue, Jan 21, 2014 at 3:35 PM, Antonis Tsiapaliokas wrote:
> I think that splitting each individual component to its own repo might be a
> bit confusing. Because if we don't have two groups (plasma-desktop and plasma-
> workspace), then we will not be able to provide something as a stand
> 1) Create two different groups named plasma-workspace and
> plasma-desktop like frameworks
> 2) Split out every component into individual repos
> 3) Assign repos to the related group.
>
> Advantages:
>
> 1) Easy to assign maintainer to individual component.
> 2) If we split only some repos, we
Martin GräßlinOn Tuesday 21 January 2014 08:32:16 wrote:
> On Tuesday 21 January 2014 01:06:36 Martin Klapetek wrote:
> > On Mon, Jan 20, 2014 at 6:59 PM, Thomas Lübking
> >
> > wrote:
> > > On Montag, 20. Januar 2014 17:29:18 CEST, Martin Klapetek wrote:
> > > How would the positioning work ins
27 matches
Mail list logo
