Re: Rethinking global shortcuts

2013-02-09 Thread Martin Graesslin
On Saturday 09 February 2013 16:51:16 Mark wrote: > A window manager should in my opinion do just that, manage windows. It > has no business in managing global shortcut keys. Or is my logic > flawed? If so, please do correct me. In a Wayland world the compositor is responsible for input and there i

Re: Re: Rethinking global shortcuts

2013-02-09 Thread Mark
On Sat, Feb 9, 2013 at 12:06 PM, Martin Gräßlin wrote: > On Friday 08 February 2013 22:25:13 Mark wrote: >> On Thu, Feb 7, 2013 at 5:56 PM, Sebastian Kügler wrote: >> > On Thursday, February 07, 2013 14:33:47 Aaron J. Seigo wrote: >> >> the "start other window manager" feature(/bug? ;) >> > >> >

Re: Re: Rethinking global shortcuts

2013-02-09 Thread Martin Gräßlin
On Friday 08 February 2013 22:25:13 Mark wrote: > On Thu, Feb 7, 2013 at 5:56 PM, Sebastian Kügler wrote: > > On Thursday, February 07, 2013 14:33:47 Aaron J. Seigo wrote: > >> the "start other window manager" feature(/bug? ;) > > > > In the new world, this might be an old concept that we don't ha

Re: Rethinking global shortcuts

2013-02-08 Thread Mark
On Thu, Feb 7, 2013 at 5:56 PM, Sebastian Kügler wrote: > On Thursday, February 07, 2013 14:33:47 Aaron J. Seigo wrote: >> the "start other window manager" feature(/bug? ;) > > In the new world, this might be an old concept that we don't have to drag > over. The traditional need for this will prob

Re: Rethinking global shortcuts

2013-02-08 Thread Mark
On Thu, Feb 7, 2013 at 2:51 PM, Aaron J. Seigo wrote: > On Thursday, February 7, 2013 14:32:06 Marco Martin wrote: >> So an application could listen for global named shortcuts and then register >> own if those are not enough > > +100 > >> then shortcuts could all have names like >> >> org.kde.comm

Re: Rethinking global shortcuts

2013-02-08 Thread Sebastian Kügler
On Thursday, February 07, 2013 14:33:47 Aaron J. Seigo wrote: > the "start other window manager" feature(/bug? ;) In the new world, this might be an old concept that we don't have to drag over. The traditional need for this will probably be mostly gone. If we want to remove it, the move to Wayla

Re: Rethinking global shortcuts

2013-02-07 Thread Rick Stockton
My only comments are at the bottom, and semi-OT. On 02/07/2013 05:51 AM, Aaron J. Seigo wrote: > On Thursday, February 7, 2013 14:32:06 Marco Martin wrote: >> So an application could listen for global named shortcuts and then register >> own if those are not enough > +100 > >> then shortcuts coul

Re: Rethinking global shortcuts

2013-02-07 Thread Martin Graesslin
On Thursday 07 February 2013 18:51:41 Kevin Ottens wrote: > On Thursday 7 February 2013 14:33:47 Aaron J. Seigo wrote: > > this would mean work on our part in the kglobalshortcut code in kdelibs > > for > > frameworks 5 and would imply that we take full maintainership of this area > > of things. >

Re: Rethinking global shortcuts

2013-02-07 Thread Kevin Ottens
On Thursday 7 February 2013 14:33:47 Aaron J. Seigo wrote: > this would mean work on our part in the kglobalshortcut code in kdelibs for > frameworks 5 and would imply that we take full maintainership of this area > of things. Please! Especially because a) I love what I read so far in that th

Re: Rethinking global shortcuts

2013-02-07 Thread Aaron J. Seigo
On Thursday, February 7, 2013 14:59:58 Martin Gräßlin wrote: > remember that Wayland doesn't allow applications to just listen to key > events. If we design something new (like a framework) it should keep that > case in mind. so we will need an external process. ok .. then i agree with your origin

Re: Re: Rethinking global shortcuts

2013-02-07 Thread Martin Gräßlin
On Thursday 07 February 2013 14:41:00 Marco Martin wrote: > On Thursday 07 February 2013, Aaron J. Seigo wrote: > > >From a technical point of view I just want to note that with Wayland > > >input > > > > > > handling moves in the compositor anyway, so we need to work on it either > > > way. I woul

Re: Re: Rethinking global shortcuts

2013-02-07 Thread Martin Gräßlin
On Thursday 07 February 2013 14:33:47 Aaron J. Seigo wrote: > one way around this could be to have the shortcut handling encapsulated in a > library and kded would be simply be a backup, but kwin would normally take > the dbus interface over. I was thinking in the direction of KWin taking the dbus

Re: Rethinking global shortcuts

2013-02-07 Thread Aaron J. Seigo
On Thursday, February 7, 2013 14:32:06 Marco Martin wrote: > So an application could listen for global named shortcuts and then register > own if those are not enough +100 > then shortcuts could all have names like > > org.kde.common.media.forward > org.kde.common.fullscreen > org.kde.workspace.

Re: Rethinking global shortcuts

2013-02-07 Thread Marco Martin
On Thursday 07 February 2013, Aaron J. Seigo wrote: > >From a technical point of view I just want to note that with Wayland input > > > > handling moves in the compositor anyway, so we need to work on it either > > way. I would prefer to get the global shortcut handling already right now > > > int

Re: Rethinking global shortcuts

2013-02-07 Thread Aaron J. Seigo
On Thursday, February 7, 2013 13:43:46 Martin Gräßlin wrote: > This situation *sucks*. you just described exactly the problems i noted sometime around 4.0. i gave up trying to get change somewhere around 4.2 or so. the maintainer of the current system simply disagrees that what you and i find to b

Re: Rethinking global shortcuts

2013-02-07 Thread Marco Martin
On Thursday 07 February 2013, Martin Gräßlin wrote: > Hi all, > > I just wanted to add another global shortcut to KWin and found the > situation so disappointing that I think we should do something about it in > PW2. > > So what happened: I wanted to add a new shortcut for showing application > m