X2Go Bug report logs - #364
Please add config option to disable bubble help text and change the wording of it

Full log

Message #25 received at 364@bugs.x2go.org (full text, mbox, reply):

Received: (at 364) by bugs.x2go.org; 14 Dec 2013 21:46:01 +0000
From newsgroups.mail2@stefanbaur.de  Sat Dec 14 22:46:00 2013
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,
	RCVD_IN_DNSWL_BLOCKED,SPF_HELO_PASS autolearn=ham version=3.3.2
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9])
	by ymir (Postfix) with ESMTP id 946345DB20;
	Sat, 14 Dec 2013 22:46:00 +0100 (CET)
Received: from [192.168.0.3] (dslb-188-099-196-058.pools.arcor-ip.net [188.99.196.58])
	by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis)
	id 0MY4Jc-1W56Cl2N0a-00Vc0N; Sat, 14 Dec 2013 22:45:59 +0100
Message-ID: <52ACD1A3.2060901@stefanbaur.de>
Date: Sat, 14 Dec 2013 22:46:11 +0100
From: Stefan Baur <newsgroups.mail2@stefanbaur.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, 
 x2go-dev@lists.berlios.de, Ricardo Díaz Martín
 <oceanosoftlapalma@gmail.com>
CC: 364@bugs.x2go.org, submit@bugs.x2go.org
Subject: Re: [X2Go-Dev] Bug#364: Please add config option to disable bubble
 help text and change the wording of it
References: <52A876A2.8090104@stefanbaur.de> <CAPWth0Jx2zL=21WwrVcDZj-x+1UgEBiYaOafV=umNjRA8=893w@mail.gmail.com> <20131214212412.Horde.NQysMgnYNgsDhh6jb88Eag5@mail.das-netzwerkteam.de>
In-Reply-To: <20131214212412.Horde.NQysMgnYNgsDhh6jb88Eag5@mail.das-netzwerkteam.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:WyGXh71M4eaI07SXQjZGYzgM5ERiI5qMQlXhzzA6jlZ
 c4DEiFfI0KlfQKJM6M7Z6wUgs/m7lcDwwmyXcghAWihlGbZMVZ
 OReLaAJ4dkw3Z/baxttXPKzCgLeWXPIL9pUST95eUgiJ52/uNG
 qKMPnGnjRQ5K72f0LWMC0az1z1cx6d6r294LpAKA+v2X765snx
 qTcOHM1eb1JBaWdt5ZcbkK+Z8YNK6a/b3s/yl3IswgFL+IpMdg
 WLtiJyJTnnygJvoAD0Cp6N1MiP9cpbmyPnK2BWdzds5ozMUbG0
 hiUGU+gJnd2TQJSewRpFJDkkeUlmq9ZGt96HtgieDO4jdcoIQt
 gdJ4oIzUoCZBcmqgJeus3SsQITBcZMDFZLHKl8+bR

Am 14.12.2013 22:24, schrieb Mike Gabriel:

> /me shyly raises his hand...
>
> I don't care too much for the session name in the bubble. I find it very
> helpful, but I lack normal user perspective, of course. However, I also
> think that we should make the bubble configurable. Actually it might be
> nice to be able to switch notifications on and off in the session
> profile. The default should be: bubbles turned on.

And that's just the point. You're a developer. You need debug messages. 
Displaying a session name for that reason is totally okay, and I can see 
why you want those info bubbles with that content.
BUT:
1) The session name (i.e. the pseudorandom mumbo-jumbo, not the "human 
readable name" - it's okay to display that one to a regular user) should 
only be displayed inside the bubble if the client is in "debug mode". 
Either by adding a --debug or by ticking a checkbox in the options.
2) In debug mode, the message should appear for a longer period of time, 
so that you have a chance to copy and paste it. For me, it disappeared 
before I had a chance to even move my mouse over it from the center of 
my screen. And no, I'm not using a 100" screen. ;-)
3) I still believe that the best way to solve the issue would be to make 
it configurable, like:
- If "Debug" is set, always pop up, display the cryptic name along with 
the session name, and stay visible for at least 10 seconds
- If "Debug" is not set, but "Autostart" is set, completely hide the 
bubble. (optional)
- If neither is set, display the bubble for 4-5 seconds, only showing 
human readable information.

An ordinary user *will* be confused and irritated by that extra info.

[...]

> @Ricardo: Stefan is one of those persons who is very supportive to X2Go
> behind the scenes. He also already contracted Alex for e.g. development
> of the published applications support.

Thanks for putting that into perspective, Mike#1.


> @Stefan: supposing that someone adds ,,silly eye candy'' can be
> insultive, indeed. It's always good to check with the contributors (see
> debian/changelog) and check for the use case and give feedback during he
> development phase (and not 5 minutes before the releases is due). (->
> X2Go Client from the nightly builds for Debian and Ubuntu had the
> bubbles for 2-3 months now and noone complaint so far).

The thing is, so far, I'm only using the Windows client in my daily 
business, so I don't have a chance to catch those changes early on, 
unless you manage to provide nightlies for Windows as well.

The TCE stuff I'm working on in my free time is used by my 68-year old 
Dad (and I'm preparing a second ThinClient for my Mom), and I don't want 
to (ab)use him as a guinea pig for new X2Go features, so I'm not 
updating his client/server installations (aside from security patches - 
 the sources.lists on his machines actually exclude the regular debian 
archive and only include security.debian.org and the x2go wheezy repo) 
unless absolutely necessary.
And for my own personal computer, while it's dual-boot, I'm using 
Windows 7 most of the time, even off duty. Kind of sad, but true - and 
also a usability issue (the move from KDE3 to Win7 was easier than the 
move from KDE3 to KDE4 - and IMO, that's *not* because the Microsoft 
guys did a particularly good job with Win7 *hint, hint*).

Okay, enough ranting for today.

Kind Regards,
Stefan

Send a report that this bug log contains spam.