Solution #2:
Use same window animation as "Minimize" , but toward the indicator in systray
When you minimize a window, there is an animation (zoom) that gives the feeling that the window is reduced toward the bottom of the screen until its final reduced location in the . This idea is to use the same zoom animation for reduction in systray !
Some applications already use this system for systray reduction : for example in Lucid, Empathy with Telepathy's PPA (ppa:telepathy/ppa) has its indicator in the Notification Zone, and uses this animation. Just try it !
When you minimize a window, there is an animation (zoom) that gives the feeling that the window is reduced toward the bottom of the screen until its final reduced location in the . This idea is to use the same zoom animation for reduction in systray !
Some applications already use this system for systray reduction : for example in Lucid, Empathy with Telepathy's PPA (ppa:telepathy/ppa) has its indicator in the Notification Zone, and uses this animation. Just try it !
Solution #3:
Display messages.
Written by
Lachu the 12 Sep 10 at 08:38.
- Display information how many windows have application this window belongs to on mouse hover close button.
- Display messages, when window, which don't have focus lastly time disappears(message like "task is complete")
- Tray icon is yet another window
- Watch on x server connections (especially when user interact with window of this application) and show messages, when connection is closed.
- Display information how many windows have application this window belongs to on mouse hover close button.
- Display messages, when window, which don't have focus lastly time disappears(message like "task is complete")
- Tray icon is yet another window
- Watch on x server connections (especially when user interact with window of this application) and show messages, when connection is closed.
Solution #4:
Use emule's technique: a button for closing, a button for the tray
Written by
knocte the 15 Sep 10 at 20:10.
You can see an example of what I mean by seeing this image:
https://bugzillafiles.novell.org/attachment.cgi?id=389828
Of course, still the applications that add this button should add a warning message when the close button is pressed. But this way the user instantly sees there is an extra button that he wants to know about.
And this way it's easy to spot which applications have this functionality and which don't.
Furthermore, this idea could be combined with Solution#2 too to make the user experience even clearer.
You can see an example of what I mean by seeing this image:
https://bugzillafiles.novell.org/attachment.cgi?id=389828
Of course, still the applications that add this button should add a warning message when the close button is pressed. But this way the user instantly sees there is an extra button that he wants to know about.
And this way it's easy to spot which applications have this functionality and which don't.
Furthermore, this idea could be combined with Solution#2 too to make the user experience even clearer.
Solution #5:
Use MSN Messenger's technique: solution #2 +display a notification
Written by
Glaedr the 20 Sep 10 at 13:19.
Minimize the app to the tray and display a notification such as "The [appname] app is still running in the tray, right-click and select Quit to close it" or similar.
Minimize the app to the tray and display a notification such as "The [appname] app is still running in the tray, right-click and select Quit to close it" or similar.
Solution #6:
Use a different button if closing the window will send the app to tray
Instead of the red X the button could be orange or something instead, or some other icon that indicates sending to tray.
Instead of the red X the button could be orange or something instead, or some other icon that indicates sending to tray.
Solution #7:
Make an system tray-program
Written by
TooSmart the 4 Oct 10 at 01:05.
This program will give permissions to which apps should be killed and which ones should be in the system tray based on the user's preference.
This program will give permissions to which apps should be killed and which ones should be in the system tray based on the user's preference.
Solution #8:
"Cannot be closed" in the taskbar
When the user want close the window, a message "cannot be close" appear in the taskbar, next to the application icon.
When the user want close the window, a message "cannot be close" appear in the taskbar, next to the application icon.
Solution #9:
Use Mac OS X's technique: closing a window never closes the application
Written by
leggy the 3 Nov 10 at 04:03.
List applications in a panel or dock, instead of windows. Applications can be closed from that list.
Then:
* The close button on a window's title bar, control+W, or file->close, closes only the window.
* The close button on the applications list, control+Q, or file->quit closes the application every time.
The Gnome window list can already group windows by application, and when you right click on the group button there is an option to close all the windows. This could close the application explicitly instead.
Clicking the button for an application with no open windows should do something useful, like open a new document.
Unfortunately, this requires altering applications so they can be open with no windows. Several applications that already remain open with no windows must also be changed, so they don't put their (non-notification) icon in the notification area.
In the transition period, you could emulate leaving an application open when its last window is closed from the title bar button by leaving the it in the application list. Closing the fake application removes the list entry. Clicking it starts it again. This isn't ideal, since the emulation could not tell if the application quit because you closed the last document or or asked to quit.
List applications in a panel or dock, instead of windows. Applications can be closed from that list.
Then:
* The close button on a window's title bar, control+W, or file->close, closes only the window.
* The close button on the applications list, control+Q, or file->quit closes the application every time.
The Gnome window list can already group windows by application, and when you right click on the group button there is an option to close all the windows. This could close the application explicitly instead.
Clicking the button for an application with no open windows should do something useful, like open a new document.
Unfortunately, this requires altering applications so they can be open with no windows. Several applications that already remain open with no windows must also be changed, so they don't put their (non-notification) icon in the notification area.
In the transition period, you could emulate leaving an application open when its last window is closed from the title bar button by leaving the it in the application list. Closing the fake application removes the list entry. Clicking it starts it again. This isn't ideal, since the emulation could not tell if the application quit because you closed the last document or or asked to quit.
Solution #10:
Create guidelines for consistent behavior
Written by
Otus the 9 Nov 10 at 11:29.
For example: Close button should always close the app; minimize may be used for "close to tray" behavior, but must be configurable. Also guide on defaults and the types of apps that should use this behavior.
For example: Close button should always close the app; minimize may be used for "close to tray" behavior, but must be configurable. Also guide on defaults and the types of apps that should use this behavior.
Solution #11:
Change color of the close button too + #2
Written by
Klau3 the 8 Dec 10 at 22:15.
One way – by side of #2 – could be to change the close button color to blue or green. This would indicate that the program would not close when clicking on it (close == red icon, indicator to systray == blue or green).
PS: I was thinking about the described problem a while ago too :)
One way – by side of #2 – could be to change the close button color to blue or green. This would indicate that the program would not close when clicking on it (close == red icon, indicator to systray == blue or green).
PS: I was thinking about the described problem a while ago too :)
Solution #12:
Different animations + Indicator
Maybe, there should be an indicator and a different desktop effect for it. IE: Clicking the X button on an application that is closing will make it fade out. But clicking the X button on an application that is just going in the background will fade and zoom towards the indicator applet, and there will be a notification that says "*** is now running in the background" (Kinda like the notification for changing the volume) A notification like this makes things feel smoother and more refined, especially on a mobile OS. And this would work for a desktop system as well.
Another way to accomplish something like this is to have it so that clicking the X button closes the app, but clicking and holding it makes it run in the background. Along with the notification.
In both cases above, there should always be a place to see what apps are running. Currently, on a fresh install, you have to go to System>Administration>System Monitor> Processes tab to see open processes. That is simply too many clicks to see running tasks.
The solution to this is to put a menu item in the Session Indicator Applet that shows running tasks and processes. It should only show apps with a window, or that have been started by the User and not by logging in to reduce clutter.
EDIT: Also do like YannUbuntu said in solution 1 and make the indicator flash/glow.
Maybe, there should be an indicator and a different desktop effect for it. IE: Clicking the X button on an application that is closing will make it fade out. But clicking the X button on an application that is just going in the background will fade and zoom towards the indicator applet, and there will be a notification that says "*** is now running in the background" (Kinda like the notification for changing the volume) A notification like this makes things feel smoother and more refined, especially on a mobile OS. And this would work for a desktop system as well.
Another way to accomplish something like this is to have it so that clicking the X button closes the app, but clicking and holding it makes it run in the background. Along with the notification.
In both cases above, there should always be a place to see what apps are running. Currently, on a fresh install, you have to go to System>Administration>System Monitor> Processes tab to see open processes. That is simply too many clicks to see running tasks.
The solution to this is to put a menu item in the Session Indicator Applet that shows running tasks and processes. It should only show apps with a window, or that have been started by the User and not by logging in to reduce clutter.
EDIT: Also do like YannUbuntu said in solution 1 and make the indicator flash/glow.
Solution #13:
Minimize-to-system-tray button in the "X close" button's place (option 3 in img
Written by
Voltius the 6 Mar 11 at 09:08.
http://www.chrisnorstrom.com/wp-content/uploads/2011/03/featured-image.png
=== There are 2 different types of programs ===
Web browsers, email and chat windows, and Photoshop are made to be interacted with and closed when done. But programs like Steam, Skype, uTorrent, instant messenger clients, virus scanners, music players, and others are designed to not be interacted with frequently and instead just allowed to run in the background while you’re working on other things.
=== The Problem ===
Is that both of these types of programs, interactables & forgettables, both use the close “X” button to do two different things. Forgettables just want to run in the background and stay out of your way, but no one bothered to give them their own button to ‘minimize to system tray’ so they use the “X” close button, which is bad because it confuses users and is inconsistent.
Most users just click towards the big red button and assume it will close the window of the program and exit the program itself. They’re probably not going to spend too much time looking at what symbol the big red button has inside of it. Also, users have gotten use to thinking that the button on the outside means close and exit.
== The Solution ==
Keep the "X" close button but scoot it over and in its place put a 'minimize to systray' button. This way everyone's happy. Users by habit will still click on the end red button and minimize the program to systray which is what the developer indented for them to do. Other users can use the "X" close button to exit the program completely.
http://www.chrisnorstrom.com/wp-content/uploads/2011/03/featured-image.png
=== There are 2 different types of programs ===
Web browsers, email and chat windows, and Photoshop are made to be interacted with and closed when done. But programs like Steam, Skype, uTorrent, instant messenger clients, virus scanners, music players, and others are designed to not be interacted with frequently and instead just allowed to run in the background while you’re working on other things.
=== The Problem ===
Is that both of these types of programs, interactables & forgettables, both use the close “X” button to do two different things. Forgettables just want to run in the background and stay out of your way, but no one bothered to give them their own button to ‘minimize to system tray’ so they use the “X” close button, which is bad because it confuses users and is inconsistent.
Most users just click towards the big red button and assume it will close the window of the program and exit the program itself. They’re probably not going to spend too much time looking at what symbol the big red button has inside of it. Also, users have gotten use to thinking that the button on the outside means close and exit.
== The Solution ==
Keep the "X" close button but scoot it over and in its place put a 'minimize to systray' button. This way everyone's happy. Users by habit will still click on the end red button and minimize the program to systray which is what the developer indented for them to do. Other users can use the "X" close button to exit the program completely.
Solution #14:
#1 + #2
Written by
ZebaSz the 14 Mar 11 at 02:24.
Highlighting the indicator helps the user focus on the specific indicator, but might be confused with another app requiring atention.
Using an animation helps understand the app is effectively still running, but the user might have a hard time finding the exact indicator.
I think using a combination of both helps the user understand the app is running on the background, and exactly where to find it again.
Highlighting the indicator helps the user focus on the specific indicator, but might be confused with another app requiring atention.
Using an animation helps understand the app is effectively still running, but the user might have a hard time finding the exact indicator.
I think using a combination of both helps the user understand the app is running on the background, and exactly where to find it again.
Propose your solution
Attachments
No attachments.
Duplicates
Comments
Apps that goes to systray instead of closing when closing them is annoying and inconsistent. Not new beginner friendly. Not natural. Takes more clicks to quit.
morion
wrote on the 11 Feb 11 at 06:56
Using Dock's as default on Linux could be nice. But there should be thought about.
How to make the best user friendly interface:
1) where to place the apps
2) your standard launchers for example: fire fox
etc.
Cairo handles this quite nice simple but still people who like to customize there things can do whatever where ever
and if there should be a discussion about the fact that dock's are user friendly the best example is my old man.
His computer knowledge is zero and he bought a Mac OS X Leopard which comes standard with docks.
He finds them easy to use but also faster to lauch the things he daily uses.
So for me go for the docks thing:
1) user friendly
2) Nice eye candy
3) if configured right they make life easier and faster
4) it wouldn't be hard job to realise because there are allot of Docky's out there.
aestus
wrote on the 23 Mar 11 at 02:18
I think the button should be contextual to it's behavior. An app that will run in the background when closed should immediately let the user know that via the hover-state of the button. Instead of a red X, it's hover-state could be a yellow button of a faded or dotted outline of an app window to show that it's closing the window only. Apps that will close out completely can have the standard red x hover-state when the user hovers over the button.
In addition, the user should be able to control click on a yellow close window button to also completely close the app, to prevent it from running in the background. Also, users should be able to simple click and hold their left click button down on the button for a few seconds to visually change the "yellow close window button" to a "red exit application" button and then release to achieve the same result.
Post your comment