Pup et all

[Thorsten Leemhuis]

Jeremy Katz schrieb:
> On Wed, 2006-09-06 at 07:10 +0200, Thorsten Leemhuis wrote:
>> Rahul schrieb:
>>> While yum in Fedora development tree is significantly faster, Pup and 
>>> Pirut still seems slow to me.  There are multiple puplet notifications 
>>> showing the number of updates which dont go away if I try to close it. [...]
>> I upgraded to the devel tree on two machines and had another minor
>> problem with puplet -- I knew that it's new in FC6 so I looked out for
>> it after the upgrade. I tried to start puplet manually and there was no
>> reaction. I looked in the list of applets and couldn't find it. It took
>> me round about ten minutes until I realized "Hey, it's there and started
>> by default and seems to use the notification area, but hides when there
>> are no updates available." (Or am I wrong with that again?) That was a
>> bit confusing. Maybe it should show up in notification area for 30
>> seconds and hide afterwards? Or it could output "I'm running already in
>> the notification area and will show up if there are updates available"
>> when you call puplet on the command line?
> The problem is that then what are you actually notifying?  "hey, I'm
> running" is hardly something that should be interesting.  The continued
> abuse of the notification area for things always being there really
> needs to stop or it's going to end up a bazillion things wide just like
> on Windows.

Agreed, I shouldn't be there always. But as I said 'It could output "I'm
running already in the notification area and will show up if there are
updates available" when you call puplet on the command line' Then people
would known what's up and people could check that puplet is running and
be sure that they'll get a notice when updates are available.

> The current behavior really is nice -- you get notified that there are
> updates when you have them.  Not before, not something sitting and
> taking up space 

+1

>> Maybe someone else has better ideas how this "confusion for the user"
>> can be avoided. But we should make sure we document this properly in the
>> release notes if we can't get the situation improved before FC6.
> I think it's largely a matter of ensuring that the expectation is set
> properly -- instead of "there's a notification applet", the feature is
> "notification of update availability".  Also, realistically, once FC6 is
> out, it won't be a problem because updates won't be long behind :-P

:-)

CU
thl