Re: Re: qml screenlocker, again

2012-08-27 Thread Martin Gräßlin
On Monday 27 August 2012 20:13:07 Marco Martin wrote: > On Monday 20 August 2012, Marco Martin wrote: > > Hi all, > > i was taking a look (and did some fixes) to the screenlocker branch of > > kde- > > workspace, with the qml replacement of the whole screensaver, used in > > plasma active. > > a t

Re: qml screenlocker, again

2012-08-27 Thread Marco Martin
On Monday 20 August 2012, Marco Martin wrote: > Hi all, > i was taking a look (and did some fixes) to the screenlocker branch of kde- > workspace, with the qml replacement of the whole screensaver, used in > plasma active. a thing that surfaced during the review: was there ever done any documentat

Re: qml screenlocker, again

2012-08-22 Thread Marco Martin
On Tuesday 21 August 2012, Martin Gräßlin wrote: > > > oh, another thing.. what about widgets on screensaver? is something that > > we really want to keep? > > should still work, IIRC I adjusted it. Personally I would like to have it > as the default, but it's too slow in loading. is on review n

Re: qml screenlocker, again

2012-08-22 Thread Marco Martin
On Tuesday 21 August 2012, Alex Fiestas wrote: > On Tuesday 21 August 2012 17:51:55 Martin Gräßlin wrote: > > should still work, IIRC I adjusted it. Personally I would like to have it > > as the default, but it's too slow in loading. > > Then we should try to improve this somehow (Maybe in randa?)

Re: Re: qml screenlocker, again

2012-08-21 Thread Martin Gräßlin
On Tuesday 21 August 2012 19:20:08 Marco Martin wrote: > On Tuesday 21 August 2012, Martin Gräßlin wrote: > > > i think the timeout is still (partly) governed by the screensaver > > > timeout, so without that kcm wouldn't make much sense, should be > > > uniquely powermanagement governed timeouts?

Re: qml screenlocker, again

2012-08-21 Thread Marco Martin
On Tuesday 21 August 2012, Alex Fiestas wrote: > On Tuesday 21 August 2012 17:51:55 Martin Gräßlin wrote: > > should still work, IIRC I adjusted it. Personally I would like to have it > > as the default, but it's too slow in loading. > > Then we should try to improve this somehow (Maybe in randa?)

Re: qml screenlocker, again

2012-08-21 Thread Marco Martin
On Tuesday 21 August 2012, Martin Gräßlin wrote: > > i think the timeout is still (partly) governed by the screensaver > > timeout, so without that kcm wouldn't make much sense, should be > > uniquely powermanagement governed timeouts? > > sounds reasonable to move it to powermanagement > > > oh,

Re: Re: Re: qml screenlocker, again

2012-08-21 Thread Alex Fiestas
On Tuesday 21 August 2012 17:51:55 Martin Gräßlin wrote: > should still work, IIRC I adjusted it. Personally I would like to have it as > the default, but it's too slow in loading. Then we should try to improve this somehow (Maybe in randa?) I'd really like to have: -Unread messages -Finished jo

Re: Re: qml screenlocker, again

2012-08-21 Thread Martin Gräßlin
On Tuesday 21 August 2012 13:43:56 Marco Martin wrote: > > Three issues come to my mind: > > * log-in with locked screen (needs adjustment in startkde) > > hmm, any reason in particular this would be needed or wanted? * it's a feature currently present * it allows to not stop at KDM - very useful

Re: qml screenlocker, again

2012-08-21 Thread Marco Martin
On Monday 20 August 2012, Martin Gräßlin wrote: > > the only big issue (and is indeed, quite big) is that is possible to kill > > the window with ctrl+alt+esc key combo. > > any idea how to solve this? > > nasty, that should not be. Solution is to grab the keyboard, but that > should actually be d

Re: qml screenlocker, again

2012-08-21 Thread Marco Martin
On Monday 20 August 2012, Martin Gräßlin wrote: > > the only big issue (and is indeed, quite big) is that is possible to kill > > the window with ctrl+alt+esc key combo. > > any idea how to solve this? > > nasty, that should not be. Solution is to grab the keyboard, but that > should actually be d

Re: qml screenlocker, again

2012-08-20 Thread Martin Gräßlin
> the only big issue (and is indeed, quite big) is that is possible to kill > the window with ctrl+alt+esc key combo. > any idea how to solve this? nasty, that should not be. Solution is to grab the keyboard, but that should actually be done by ksmserver already. > > and most important: do anyone