[Bug 304964] New: Confusing launching behavior in yast2-gtk-ui vs. Application Browser

newer
[Bug 356410] New: Easier choosing...

bugzilla_noreply＠novell.com

27 Aug 2007 27 Aug '07

18:16

https://bugzilla.novell.com/show_bug.cgi?id=304964 Summary: Confusing launching behavior in yast2-gtk-ui vs. Application Browser Product: openSUSE 10.3 Version: Beta 2 Platform: Other OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME - Admin AssignedTo: bnc-team-gnome-administration@forge.provo.novell.com ReportedBy: btimothy@novell.com QAContact: qa@suse.de Found By: Development When I use the Application Browser to launch Yast, the Application Browser window disappears when I click on Yast. The same is not true once inside the Yast window. When I click on something, it appears to me that nothing is happening. So, what I end up doing is clicking on the admin item again, which ends up launching *another* instance of the item. While this behavior could be "learned" by a user, it is very confusing and not consistent. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

28 Aug 28 Aug

15:19

New subject: [Bug 304964] Confusing launching behavior in yast2-gtk-ui vs. Application Browser

https://bugzilla.novell.com/show_bug.cgi?id=304964#c1 Mark Gordon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtgordon@novell.com --- Comment #1 from Mark Gordon 2007-08-28 09:19:56 MST --- If the YaST shell were to close, users wanting to invoke multiple YaST modules would need to reauth for each module. One advantage of the persistent YaST shell is that you only need to provide the root password once. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:36

New subject: [Bug 304964] Confusing launching behavior in yast2-gtk-ui vs. Application Browser

https://bugzilla.novell.com/show_bug.cgi?id=304964#c2 --- Comment #2 from Boyd Timothy 2007-08-28 09:36:27 MST --- Yeah, I understand the drawbacks of closing the window and I'm not suggesting that's the solution to this problem. What really needs to happen is that the user gets some feedback that a program/module is being launched. Ignoring some possible technical impossibilities of these options, some ideas for improving the situation might be (not an all-inclusive solution list): 1. Disable all the other module buttons until the module that's clicked on is running. 2. Change the mouse pointer to an hourglass/timer to show that the machine is doing something (less effective since the user could still press the same module button again). 3. Open the module in the same window, just like web browser behavior. This one is kind of limiting since it means you'd only access one module at a time. But then again, perhaps tabs (like tabbed-browsing) might solve this. Little things like this are greatly needed to add polish to the GNOME Desktop experience. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:27

New subject: [Bug 304964] Confusing launching behavior in yast2-gtk-ui vs. Application Browser

https://bugzilla.novell.com/show_bug.cgi?id=304964#c3 --- Comment #3 from Mark Gordon 2007-08-28 10:27:54 MST --- Nu, you *don't* want it consistent with the application browser? ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:32

New subject: [Bug 304964] Confusing launching behavior in yast2-gtk-ui vs. Application Browser

https://bugzilla.novell.com/show_bug.cgi?id=304964#c4 --- Comment #4 from Boyd Timothy 2007-08-28 10:32:14 MST --- I'm just pointing out that the whole thing is a problem. One of the problems is that it's not consistent with how Application Browser works. It's conceivable that users have learned the behavior of Application Browser and then be surprised when Yast Control Center doesn't behave the same way (since it practically looks the same). The bigger problem is that it's hard for a user to know that a module is being launched since there's no graphical feedback that anything is happening after a user clicks a module button. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.