After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 609828 - Vinagre first-run message concept is bad and full of teachspeak
Vinagre first-run message concept is bad and full of teachspeak
Status: RESOLVED FIXED
Product: vinagre
Classification: Applications
Component: general
2.29.x
Other Linux
: Normal normal
: 3.2
Assigned To: vinagre-maint
vinagre-maint
: 652508 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-02-13 13:10 UTC by Frej Soya
Modified: 2011-08-13 12:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frej Soya 2010-02-13 13:10:46 UTC
There are many things wrong with the first-run dialog.
1) The dialog is shown before anyone actually uses the program, so it's very hard to figure out what it's actually is. Never popup a dialog before the first run. 
2) It's badly filled with gtk and system information, like "menu accelerators" "intercepted by the program" "remote machine"
3) The dialog only has one action "close", dialogs are meant to communicate user choice, not information. The user get this scary warning, a

Ways to progress:   
  * Show the information in the actual context, ie. when connected to a machine. Maybe a overlay is shown the first time some key combo is pressed. "Did you mean to XXXX?"
  * Provide the choice of enable/disabling menu accelerators together with the information. (Important!).
  * Also, the text should really avoid system concepts and menu accelerators (It's keyboard shortcuts!)
Comment 1 Bryce Nesbitt 2011-06-13 21:30:53 UTC
Agreed!
Comment 2 David King 2011-06-15 20:30:04 UTC
*** Bug 652508 has been marked as a duplicate of this bug. ***
Comment 3 David King 2011-08-13 12:13:54 UTC
I pushed a fix to master as commit a4ca4e1a4b7ad6320822cf02a21c3f4b82090dfc, thanks. I took the approach of cutting out most of the complex information, using a GtkInfoBar rather than a GtkMessageDialog and providing a button to access the help.