Re: Systray jobs

2009-05-06 Thread Rob Scheepmaker
On Tuesday 05 May 2009 18:57:49 Dario Freddi wrote: > There is not a DBus interface exportable, however for 4.4 it would be nice > if we could remove that code from PowerDevil and put it somewhere else > (ideas, anyone?) > > Rob, feel free to contact me for more clarification on this. I really thin

Re: Systray jobs

2009-05-05 Thread Dario Freddi
There is not a DBus interface exportable, however for 4.4 it would be nice if we could remove that code from PowerDevil and put it somewhere else (ideas, anyone?) Rob, feel free to contact me for more clarification on this. I really think you should use XSync over XScreensaver. On Tuesday 05 M

Re: Systray jobs

2009-05-05 Thread Riccardo Iaconelli
On Saturday 02 May 2009 15:48:55 Rob Scheepmaker wrote: > That makes me thinking: is there a easy > and well working way to determine if the computer is actually being used at > the moment (I mean some central kde facility, not having to rely on mouse > polling or stuff like that). Because in that

Re: Systray jobs

2009-05-04 Thread Marco Martin
On Friday 01 May 2009, Rob Scheepmaker wrote: > Hello all, > > I would like in discuss what things should still be improved to the way > jobs are handled in the systemtray before the freeze. These are some of the > things I noticed or are often requested: > > * Auto hiding after the dialog with job

Re: Systray jobs

2009-05-02 Thread Sebastian Kügler
On Saturday 02 May 2009 18:17:56 Rob Scheepmaker wrote: > On Saturday 02 May 2009 17:48:13 Sebastian Kügler wrote: > > On Friday 01 May 2009 18:40:00 Rob Scheepmaker wrote: > > > These are the main issues I encountered. Please try the systray from > > > trunk some time and give your feedback on the

Re: Systray jobs

2009-05-02 Thread Chani
> > > we're supposed to have some kind of logging facility, right? ideally I'd > > expect that notifications that stopped doing anything more than 5 minutes > > ago would get sent away somewhere so that I'd have to explicitly click > > some sort of "history" button or something to show them. I migh

Re: Systray jobs

2009-05-02 Thread Rob Scheepmaker
On Saturday 02 May 2009 17:48:13 Sebastian Kügler wrote: > On Friday 01 May 2009 18:40:00 Rob Scheepmaker wrote: > > These are the main issues I encountered. Please try the systray from > > trunk some time and give your feedback on these issues or provide your > > own points. > > I've been seeing a

Re: Systray jobs

2009-05-02 Thread Sebastian Kügler
On Friday 01 May 2009 18:40:00 Rob Scheepmaker wrote: > These are the main issues I encountered. Please try the systray from trunk > some time and give your feedback on these issues or provide your own > points. I've been seeing a logic issue for some time, I'll use this poke to finally tell you

Re: Systray jobs

2009-05-02 Thread Marco Martin
On Friday 01 May 2009, Aaron J. Seigo wrote: > On Friday 01 May 2009, Rob Scheepmaker wrote: > > * Auto hiding after the dialog with jobs and notifications get's > > automatically shown because one get's added. Currently this is hardcoded > > to 6 seconds, but there are quite some requests for havi

Re: Systray jobs

2009-05-02 Thread Marco Martin
On Saturday 02 May 2009, Rob Scheepmaker wrote: > On Friday 01 May 2009 20:39:43 Marco Martin wrote: > > On Friday 01 May 2009, Rob Scheepmaker wrote: > > > * Auto hiding after the dialog with jobs and notifications get's > > > automatically shown because one get's added. Currently this is > > > ha

Re: Systray jobs

2009-05-02 Thread Rob Scheepmaker
On Friday 01 May 2009 21:53:04 Aaron J. Seigo wrote: > On Friday 01 May 2009, Rob Scheepmaker wrote: > > * Auto hiding after the dialog with jobs and notifications get's > > automatically shown because one get's added. Currently this is hardcoded > > to 6 seconds, but there are quite some requests

Re: Systray jobs

2009-05-02 Thread Rob Scheepmaker
On Friday 01 May 2009 20:39:43 Marco Martin wrote: > On Friday 01 May 2009, Rob Scheepmaker wrote: > > * Auto hiding after the dialog with jobs and notifications get's > > automatically shown because one get's added. Currently this is hardcoded > > to 6 seconds, but there are quite some requests fo

Re: Systray jobs

2009-05-02 Thread Rob Scheepmaker
On Friday 01 May 2009 20:37:48 Chani wrote: > hrrm. you say some prefer no-autohide, then suggest a way to configure the > autohide *time*. can we just offer an autohide checkbox and hardcode the > time to something reasonable? (6 seconds seems ok so far) Probably better yes. > > * I don't like h

Re: Systray jobs

2009-05-01 Thread Aaron J. Seigo
On Friday 01 May 2009, Rob Scheepmaker wrote: > * Auto hiding after the dialog with jobs and notifications get's > automatically shown because one get's added. Currently this is hardcoded to > 6 seconds, but there are quite some requests for having no auto hiding at > all. I do very much prefer au

Re: Systray jobs

2009-05-01 Thread Chani
On May 1, 2009 09:40:00 Rob Scheepmaker wrote: > Hello all, > > I would like in discuss what things should still be improved to the way > jobs are handled in the systemtray before the freeze. These are some of the > things I noticed or are often requested: > > * Auto hiding after the dialog with jo

Re: Systray jobs

2009-05-01 Thread Marco Martin
On Friday 01 May 2009, Rob Scheepmaker wrote: > Hello all, > > I would like in discuss what things should still be improved to the way > jobs are handled in the systemtray before the freeze. These are some of the > things I noticed or are often requested: > > * Auto hiding after the dialog with job

Re: Systray jobs and notifications

2009-04-14 Thread Rob Scheepmaker
On Friday 10 April 2009 19:38:24 Aaron J. Seigo wrote: > On Friday 10 April 2009, Rob Scheepmaker wrote: > > Still that doesn't make it any easier to interpret say '3/4' in front of > > a > > ah and if all are completed, then you can just say "N" instead of "N/N" ... > > so to be ++ verbose, this w

Re: Systray jobs and notifications

2009-04-10 Thread Jamboarder
Aaron J. Seigo wrote > ... > so to be ++ verbose, this would give us (where N = notification, P = job in > progress, C = job completed): > > ScenarioText > -- > 3 N3 > 3 N, 2 P3/5 > 3 N, 1 C, 1 P4/5 > 1 C, 2 P1/3 > 2 P0

Re: Systray jobs and notifications

2009-04-10 Thread Aaron J. Seigo
On Friday 10 April 2009, Rob Scheepmaker wrote: > Still that doesn't make it any easier to interpret say '3/4' in front of a ah and if all are completed, then you can just say "N" instead of "N/N" ... so to be ++ verbose, this would give us (where N = notification, P = job in progress, C = job c

Re: Systray jobs and notifications

2009-04-10 Thread Aaron J. Seigo
On Friday 10 April 2009, Rob Scheepmaker wrote: > Still that doesn't make it any easier to interpret say '3/4' in front of a > spinner. to me it says "there are four things here, three of which are completed" notifications can therefore be viewed as jobs that completed in zero time. -- Aaron J.

Re: Systray jobs and notifications

2009-04-10 Thread Rob Scheepmaker
On Friday 10 April 2009 18:58:53 Aaron J. Seigo wrote: > On Friday 10 April 2009, Rob Scheepmaker wrote: > > Well, the problem kind of is that the systray shows multiple things: > > running jobs and notifications, which are distinctively different. Still > > are they? > > both are communicating sys

Re: Systray jobs and notifications

2009-04-10 Thread Aaron J. Seigo
On Friday 10 April 2009, Rob Scheepmaker wrote: > Well, the problem kind of is that the systray shows multiple things: > running jobs and notifications, which are distinctively different. Still are they? both are communicating system or application status to the user; both might offer interactio

Re: Systray jobs and notifications

2009-04-10 Thread Rob Scheepmaker
On Friday 10 April 2009 17:50:54 Marco Martin wrote: > On Friday 10 April 2009, Rob Scheepmaker wrote: > > I've been doing some more thinking about this: what about splitting this > > up in 2 icons? One "i" icon with a number that shows the total amount of > > notifications, and the spinner with a

Re: Systray jobs and notifications

2009-04-10 Thread Marco Martin
On Friday 10 April 2009, Rob Scheepmaker wrote: > On Tuesday 07 April 2009 03:04:32 Aaron J. Seigo wrote: > > On Monday 06 April 2009, Celeste Lyn Paul wrote: > > > On Monday 06 April 2009 08:01:16 pm Aaron J. Seigo wrote: > > > > On Monday 06 April 2009, Rob Scheepmaker wrote: > > > > > On Monday

Re: Systray jobs and notifications

2009-04-10 Thread Rob Scheepmaker
On Tuesday 07 April 2009 03:04:32 Aaron J. Seigo wrote: > On Monday 06 April 2009, Celeste Lyn Paul wrote: > > On Monday 06 April 2009 08:01:16 pm Aaron J. Seigo wrote: > > > On Monday 06 April 2009, Rob Scheepmaker wrote: > > > > On Monday 06 April 2009 19:02:58 Aaron J. Seigo wrote: > > > > > wha

Re: Systray jobs and notifications

2009-04-09 Thread Chani
On April 9, 2009 11:31:28 Rob Scheepmaker wrote: > On Thursday 09 April 2009 19:55:49 Chani wrote: > > how do you warn the user if they close their laptop lid? :) > > it does make sense for all other triggers, though. > > > > ...hmm, if the warning had a sound effect I might notice when closing my

Re: Systray jobs and notifications

2009-04-09 Thread Rob Scheepmaker
On Thursday 09 April 2009 19:55:49 Chani wrote: > how do you warn the user if they close their laptop lid? :) > it does make sense for all other triggers, though. > > ...hmm, if the warning had a sound effect I might notice when closing my > laptop. *most* of the time I also wait for it to finish s

Re: Systray jobs and notifications

2009-04-09 Thread Chani
On April 9, 2009 09:08:38 Rob Scheepmaker wrote: > On Thursday 09 April 2009 17:48:20 dantti85-...@yahoo.com.br wrote: > > >Even if the icon gets some animation, it is still small and the event > > >"notification closed" is still the same, i.e. the signal remains the > > > same as the user might ju

Re: Systray jobs and notifications

2009-04-09 Thread Rob Scheepmaker
On Thursday 09 April 2009 17:48:20 dantti85-...@yahoo.com.br wrote: > >Even if the icon gets some animation, it is still small and the event > >"notification closed" is still the same, i.e. the signal remains the same > > as the user might just notice the "it's gone" and not whereto. There have > >

Re: Systray jobs and notifications

2009-04-09 Thread Rob Scheepmaker
On Thursday 09 April 2009 16:47:41 Sven Burmeister wrote: > Am Montag, 6. April 2009 16:30:21 schrieb Rob Scheepmaker: > > Hello, > > > > I wanted to discuss what I think should be improved in the plasma > > systemtray... not the spec, but the jobs/notifications. We discussed some > > of this alrea

Re: Systray jobs and notifications

2009-04-09 Thread dantti85-...@yahoo.com.br
>Even if the icon gets some animation, it is still small and the event >"notification closed" is still the same, i.e. the signal remains the same as >the user might just notice the "it's gone" and not whereto. There have been >people stating that they thought the job was done because the notifi

Re: Systray jobs and notifications

2009-04-09 Thread Sven Burmeister
Am Montag, 6. April 2009 16:30:21 schrieb Rob Scheepmaker: > Hello, > > I wanted to discuss what I think should be improved in the plasma > systemtray... not the spec, but the jobs/notifications. We discussed some > of this already at tokamak, but there's still a lot to be done if we want > this to

Re: Systray jobs and notifications

2009-04-08 Thread Rob Scheepmaker
On Tuesday 07 April 2009 14:23:49 Rob Scheepmaker wrote: > Yeah, it contains notifications (both 'normal' and file completed), and > jobs, so indeed it may not be entirely optimal. However, both the in > progress jobs and the completed jobs belong to an ExtenderGroup. The thing > that might help is

Re: Systray jobs and notifications

2009-04-07 Thread Rob Scheepmaker
On Tuesday 07 April 2009 03:20:40 Celeste Lyn Paul wrote: > On Monday 06 April 2009 09:04:32 pm Aaron J. Seigo wrote: > > On Monday 06 April 2009, Celeste Lyn Paul wrote: > > bonus is that we already have the spinner and we've been using it around > > kde (plasma, gwenview, dolphin .. i keep seeing

Re: Systray jobs and notifications

2009-04-06 Thread Celeste Lyn Paul
On Monday 06 April 2009 09:04:32 pm Aaron J. Seigo wrote: > On Monday 06 April 2009, Celeste Lyn Paul wrote: > > I think the idea of using animation to indicate a current job running is > > a good idea. Is there an icon designed for this yet? At first I thought > > of an animated Down arrow (a met

Re: Systray jobs and notifications

2009-04-06 Thread Aaron J. Seigo
On Monday 06 April 2009, Celeste Lyn Paul wrote: > On Monday 06 April 2009 08:01:16 pm Aaron J. Seigo wrote: > > On Monday 06 April 2009, Rob Scheepmaker wrote: > > > On Monday 06 April 2009 19:02:58 Aaron J. Seigo wrote: > > > > what about the busy widget we have? we could just use that, with a >

Re: Systray jobs and notifications

2009-04-06 Thread Celeste Lyn Paul
On Monday 06 April 2009 08:01:16 pm Aaron J. Seigo wrote: > On Monday 06 April 2009, Rob Scheepmaker wrote: > > On Monday 06 April 2009 19:02:58 Aaron J. Seigo wrote: > > > what about the busy widget we have? we could just use that, with a > > > number in the middle of it showing how many jobs are

Re: Systray jobs and notifications

2009-04-06 Thread Aaron J. Seigo
On Monday 06 April 2009, Rob Scheepmaker wrote: > On Monday 06 April 2009 19:02:58 Aaron J. Seigo wrote: > > On Monday 06 April 2009, Rob Scheepmaker wrote: > > > * job widget layout. I don't know about the rest of you, but I think > > > this could be improved. The widget takes up quite some space

Re: Systray jobs and notifications

2009-04-06 Thread Rob Scheepmaker
On Monday 06 April 2009 19:02:58 Aaron J. Seigo wrote: > On Monday 06 April 2009, Rob Scheepmaker wrote: > > * job widget layout. I don't know about the rest of you, but I think this > > could be improved. The widget takes up quite some space vertically. I'm > > not sure how we can keep the widget

Re: Systray jobs and notifications

2009-04-06 Thread Aaron J. Seigo
On Monday 06 April 2009, Rob Scheepmaker wrote: > * job widget layout. I don't know about the rest of you, but I think this > could be improved. The widget takes up quite some space vertically. I'm not > sure how we can keep the widget compact while still showing all the > information (we'll need t