Bug 117288

Summary: severe usability degradation for going online
Product: [Unmaintained] kopete Reporter: Leo Savernik <l.savernik>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: bitrain
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Leo Savernik 2005-11-29 17:46:10 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Compiled From Sources

Up to and including KDE 3.4, going online was a two-step process in Kopete (using the default toolbar button configuration):

1. Click "Set status" button
2. Click "Online"

Done.

You could streamline the process even more by putting the online action into the toolbar.

Then going online boiled down to:
1. Click "Online"


Since KDE 3.5, the every status action except "Offline" have become submenues!

Hence, going online under a default configuration now takes these steps:
1. Click "Set status"
2. Aim at "Online" and hover (or click)
3. Wait for the submenu to appear
4. Reorient and select something (There's no "default", hence using the feature the first time confuses one to no end. I guess "no message" is roughly equivalent some "default").

Not only does this double the count of steps necessary to perform such a single task like going online, it also incurs an disproportionately high increase in time lost by aiming.

If you streamline the process by putting the "Online" and "Offline" actions into the toolbar, the "Online" action manifests itself as an overly long combo box.

As the kopete window is normally reduced to a small horizontal extent, replacing "Set status" with "Online" forces all other actions into the spillover-menu. This cripples the usefulness of toolbar buttons.

This all boils down to the problem that there's no more single action that *simply* goes online.

I consider this a usability bug. You may convert it to a wishlist item if you think it fits better.

It doesn't change the fact, however, that Kopete's usability is greatly diminished in this regard for the whole KDE 3.5 series (which is going to last years!)
Comment 1 Chani 2005-11-30 18:26:16 UTC
> It doesn't change the fact, however, that Kopete's usability is greatly diminished in this regard for the whole KDE 3.5 series (which is going to last years!)


I agree. this "feature" drives me nuts! I think it's one of those
things that seemed like a great idea at the time... like clippy... :P
the whole online/away/offline thing is getting to be a mess imho. I
wonder how hard it would be to make a button that would simply connect
all my accounts regardless... maybe I'll try when my darn comp stops
freezing.
Comment 2 Thiago Macieira 2005-12-01 03:45:19 UTC
I just wish you guys had mentioned it a couple of months ago, when this feature was introduced.

Not only did no one complain before the feature and message freeze, no one complained between that and the release.

So, live with it until KDE 4.
Comment 3 Thiago Macieira 2005-12-01 03:46:12 UTC
(Idea comes to mind) Or until Kopete 0.12.
Comment 4 Leo Savernik 2005-12-05 21:34:36 UTC
Am Donnerstag, 1. Dezember 2005 03:45 schrieb Thiago Macieira:
> Not only did no one complain before the feature and message freeze, no one
> complained between that and the release.


Well, it can easily be fixed without breaking i18n or BC. Just change the ugly 
combobox to a toolbar button with popup menu that works the same like 
Konqueror's back button. If you click on it, it will execute the default 
action (go Online without asking further questions), otherwise, if you wait 
briefly or move the mouse, you will get the popup-menu with the same choices 
you now get by the dropdown box.
Comment 5 Randy Carpenter 2005-12-13 00:48:21 UTC
I also noticed this. It took me quite a while to figure out that it was actually designed to operate like this. Why did someone figure that removing such an obvious option as the "Online" button was a good idea? How could the current behavior have any benefit at all? If I want to have a message set, the I can mark myself as 'away'

Please return this function to normal.
Comment 6 Jason Keirstead 2005-12-19 14:22:08 UTC
Adding my vote.

And just a reply to #2 from Thiago - I always use auto-connect, so I never realized how annoying this was until I had to re-install and did not re-enable auto-connect yet.

BTW, this in itself seems weird to me, how the user is forced to pick an online message if they manually connect, but if they auto-connect they are not? What is selected when you auto-connect?

Comment 7 arne anka 2006-01-09 16:20:28 UTC
added my vote -- i still don't understand how a button in the "customize toolbar"-menu becomes a big combo-box ...
Comment 8 Arend van Beelen jr. 2006-01-22 12:43:57 UTC
Adding my vote as well. It is extremely annoying, not only when going online but also when you go away or any of the other states (except Invisible and Offline). Another annoying side-effect is that because you are forced to select an away-message, any away-message you may have set before is automatically discarted. This undermines the usefulness of the Now Listening plugin and other custom set messages.
Comment 9 Will Stephenson 2006-01-22 16:48:15 UTC
Fixed in Kopete 0.12, have patience!

Status and Status Message are now separated so you have one action menu to set status - so you can connect in 2 clicks.  The Status Message menu is independent so any message chosen persists.

I'll also get the original Online button back so that people who want to connect in _1_ click can add it to their toolbars.
Comment 10 Leo Savernik 2006-01-22 19:56:23 UTC
Am Sonntag, 22. Januar 2006 16:48 schrieb Will Stephenson:
> ------- Fixed in Kopete 0.12, have patience!


Yippieh! Will it be located in cvs^Wsvn ready to be downloaded and built 
against KDE 3.5?
Comment 11 Olivier Goffart 2006-01-22 20:16:48 UTC
it's in the 0.12 dev branch
see instruction here:
http://wiki.kde.org/tiki-index.php?page=Kopete+XHTML%2BCSS
Comment 12 Olivier Goffart 2006-03-11 10:53:51 UTC
*** Bug 113966 has been marked as a duplicate of this bug. ***