Ubuntu 11.04 will remove the notification area (systray)
design.canonical.com
design.canonical.com
They've already done the experiment with removing update notifications from the notification area (names point at the irony here). Instead we got a system approved pop-under, 200+ people complaining in the bugreport and Mark saying something like: That's how it's going to be, now be quiet. It was the same for window button placement lately. And that's a reason I'm upgrading to Debian this time instead of 10.04.
There's some new "pad" thing that does exactly that.
Then again, if most people aren't that concerned with the file hierarchy, then why foist it on them?
There's some new "pad" thing that does exactly that.
We'll see how this unfolds. I suspect that the UI of the iPhone OS has conditioned people to think of files and items as being "in" an app. I suspect that Apple will implement some way of sharing or transferring files between apps.
Actually, KDE did it first: the application indicators specification started as what was basically a port of KDE's KStatusNotifier.
"But, we're not afraid of making bold moves. Ubuntu itself was a bold move, and has attracted a fair amount of criticism for its very existence, but that didn't stop us. If we want to transform the Linux desktop from where it is today, to something that Apple will feel obliged to emulate in parts, we are going to have to make bold moves and big changes, and those will cause distress. If we're right, the result will be fantastic, and the changes will be embraced by other distributions and upstream. If we're wrong, they won't."
Unfortunately many people get the feeling they're trying a lot of things without enough thought put into it - and when people report problems as bugs, Mark steps in and says no. They're simply becoming something like Apple of Linux world.
As another example, I have been running 10.04 beta for a while. At first I disagreed with their choice of moving all the window controls to the left, but now I am used it and actually like it better. I think it is more "efficient" as it usually minimizes my mouse movement. What is the point of this rambling? Ubuntu did something they thought was right, but wasn't popular initially. Eventually many people realized it is a better design choice. Apple (and GNOME in the Linux desktop world) have taken the same approach before. Sometimes it backfires but often it works well.
Are you left handed? I tend to keep my cursor on the right presumably as an extension of the desktop metaphor - reaching across to the right means a far larger movement.
However, I can see theoretically that if you have your application launch button ("Start", "K" or what have you) on the left that you'd want to push other things that way. However I'd rather move the "pin" and "menu" buttons to the R of the menu bar.
I trust if KDE ever went that way they'd make it an option.
No. The reason it is more efficient is because the mouse pointer usually hovers more around the left and upper edges of the windows. That is where all the most frequent menus live are and most often used toolbar buttons. You can think of it as the logical origin of the window. For example the 'File->Save As..." menu, the "File->Close" menu, the "Back & Home" buttons on the browser and so on.
It would be an interesting HCI project to run a background statistics gatherer that would record mouse coordinates relative the window in focus.
The only time I usually move the mouse to right is to scroll (but I personally use the mouse wheel for scrolling) and resize the window. But most of the time it hovers on the left side.
Also, just because you hold the mouse in the right hand doesn't say anything where the cursor is on the screen. You would have to consider where the cursor already is when you want to close/minimize/maximize the window and how far you would have to "travel" with it.
Another 2 things to consider:
1) Mouse travel might seem like a very small change, but the action of closing a window is very frequent. So a small change multiplied many times can add to quite a bit.
2) This ends up working even better for laptops since a trackpad already offers a fairly small working surface compared to the surface available for a desktop mouse. The shorter the distance the cursor moves, the less trackpad "strokes" one has to perform.
EDIT: formatting & syntax
It would indeed.
My mouse cursor definitely lives at teh right about 2/10 in from the right screen edge.
I do use shortcuts to access menus (as well as mouse, I'm fickle) but would see your comments as reasons to invert the menubar menu order and arrange them from the right rather than reason to move other stuff left.
But I'm probably an anomaly. In MS Windows (which I rarely use) my Vista install has the taskbar [vertically] on the right.
HN's reply button often annoys me because it is left aligned whilst as I'm a L-R text reader the proper position to me would be the right as on completion that is where my gaze falls.
KDE dialogs usually have Cancel/OK on right and help and other auxiliaries on the left. For example the systemsettings dialog has "apply" on the right, which inline with my above thinking seems the correct position.
Physical mouse travel for someone with all left-aligned action buttons could still be greater than someone using a "fast" mouse with action inputs spread across the screen.
There was a link posted here a day or two ago about the secret to Apple's success - they don't do focus groups, they don't have big surveys about what will and won't work. They just do, and when you have capable, knowledgeable people at the helm people will get behind you.
I see this as the same thing.
> "Why not have a wrapper for the notification area that turns it into a menu, for a last resort?"
This doesn't work, it has never worked. Just look at Windows: "hey devs, we've deprecated this horrifying monstrosity that should never have seen the light of day. For the sake of compatibility we've preserved some functionality, but please switch over to the new better thing soon"
Developers: "meh"
Let's be honest, desktop Linux UI right now is really just a (bad) clone of Windows 2000.
So Gnome isn't going to fix their UI on their own - but yet that's what your users are interacting with every single day. I for one am glad that Ubuntu is fixing what the Gnome team has demonstrated for years that they cannot/will not.
Here's the way I see it: either we continue to sit and hope in vain that Gnome will step up and do something great with their UI... or somebody else takes charge at the cost of fracturing the community. For the sake of desktop Linux, I choose the latter.
I thought anyone was allowed to fork any free software, and was encouraged to do so if they don't like the existing direction?
If they really want to fork Gnome, just be honest and say, "Gnome sucks, we're forking it and calling it "Gnomebuntu".
Use alltray: [quote] Dock any application in the tray
With AllTray you can dock any application without a native tray icon into the system tray. It works well with GNOME, KDE, XFCE 4, Fluxbox, and WindowMaker. [/quote]
PS.
I prefer to use switch-or-exec plugin in Sawfish at hot-key: I will press hotkey, Sawfish will switch to application desktop area and then bring application window. If application is not running, then Sawfish will run it. Configuration is very simple: regexp for window title or window properties to find application window and command line to execute when application window is not found.
For example, I can press "Alt-Shift-e" to switch to editor window to enter few notes. If editor is not found, then new editor will be run. When I will finish, I will press "Alt-Shift-b" to switch back to browser, "A-S-m" for mail, "A-S-i" for IDE, "A-S-t" for terminal, and so on.
I did a double take right there.
Watching the debate over new window control placement and removing the systray reminds me it's nice to be a little off the beaten path. :)
I'll suspend judgement till I actually use whatever they come up with though.
* Why isn't this app in the taskbar?
* What does close window do for this app?
* What does minimize do for this app?
* What does file quit do?Applications could then act differently based on where they were minimised - e.g., icon animations to convey a message, can't steal window focus, can show little alerts/messages, etc.
Personally, I hate when applications like rhythmbox crowd the notification area. There is no event involving rhythmbox that I will ever want to be notified of. "I'm still playing that song. Still playing. Still playing. OK, now it's over." Gee, thanks. I figure if an application has nothing new to tell me, it should stay over in the taskbar with all the other ones.
But indeed, a notification icon can do things that a taskbar entry can't. Notably, the context menu in the taskbar is defined by the taskbar, not the application, so things that take one step with a notification icon take two or more via the taskbar.
So now I think the problem isn't the notification area, it's the taskbar. Maybe if the taskbar worked better, developers wouldn't pollute the notification area so much.
As a kubuntu user, I've always hoped I'm getting a vanilla KDE with ubuntu's packaging; I want all KDE programs to work out of the box. Is KDE similarly altered by canonical? This move seems like it can only further fragment Linux.
-- The pulse audio fiasco
-- The network manager that couldn't manage anything but vanilla networks (I hear that's changed now, but I'm not about to sacrifice any more nights of my life to Ubuntu for finding out)
-- Massive and arbitrary changes to the windowing buttons without so much as a nod to keeping the actual community involved
-- Brown, then purple
-- Core application that deletes your whole drive if you don't supply parameters. Now that's pretty bad...but the clincher is that when questioned about it, the senior Ubuntu developer gave us a most excellent entry to add to the encyclopedia of bad ideas
-- And now, no system tray, "we don't like it so we throw it out" haha
I have a feeling the revolution will not be Ubuntu-ized.
ubuntus network manager has been first class for ~2 years, I have less problems on ubuntu that I do with my mac in regards to broadband dongles, its audio has also been long fixed
the aesthetic changes (purple to brown) are a large improvement that everyone asked for, the window buttons really dont matter that much (and they can be moved back)
the core application was very much a niche issue for those messing around inside a bootloader, its not like opening notepad ran rm -rf /
and as for the system tray, im not particularly fussed either way, but I am glad that someone is worrying and doing something about ui issues instead of sticking to the status quo
I use a LAN; I don't want a network manager. I use a desktop; I don't want a power manager. I have speakers; I don't want a sound manager.
If there's a way to hide them, it's not simple. You can't just uninstall them, because they've taken over the duties of actually managing the resources as well, in addition to just showing me information I don't want.
If you want to remove the feature, deprecate it. Turn it off in all new installs, leave it as is in all upgrades, and optionally notify the user about the deprecation.
However, I've written a small applet that uses notifications and I don't quite understand how things will change when what he describes happens. I have not upgraded it because the notification mechanism in karmic sucks.(I will update the code when I finally install Lucid)
Does anybody know? Will applets disappear completely?
I'm forever getting mixed up between the status menu and the messaging menu. The only thing I really use them for is Empathy, which now seems to be split between two menus. And to bring up the contact list it now takes two clicks (or more often three because I clicked the wrong menu) instead of one.
I don't like to just minimize Empathy or Rhythmbox since that gets in the way of my "working set". As a programmer working on distributed systems I often have perhaps up to a dozen windows in a workspace in each of eight workspaces. "System" stuff gets in the way of my window management. I'd like this stuff to be somewhere distinctly different.
> No competent designer, sitting down to design an operating system from scratch, would say to themselves “I know, let’s have two completely inconsistent ways to hide windows”.
I disagree with this. I want two different ways, because they have two different purposes. One is my for the working set: stuff that I'm doing. The other is for stuff that's always there, like a new email notification, an IM contact list, background music and the clock. I don't see a problem here.
I think that a notification bubble worked just fine for notifications. You'd have the icon pointed out to you, and then it would be there in the background using minimal space until you attended to it. That's about as unobtrusive as it gets. Grabbing clicks has never been a problem for me, but not being able to see under it has. I'd prefer to be able to close the notification bubble rather than being forced to wait; being able to click through is pointless if I can't properly see through.
Instead I now have an annoying popup telling me that I should update appearing in a separate window that I have to close only for it to pop up again. I understand that this is intended to be improved, but at the moment it seems to keep demanding attention and interrupting me and then it forces me to wait while it loads.
I suppose that the problem is that as an experienced user I know what the notification icon for "updates available" meant and I want it to stay there as a reminder. However, I only want to be interrupted once. At the moment (on Karmic) I get interrupted repeatedly and the only way to stop this is to remove the notification entirely.
I agree that the UI should be consistent. I would prefer if any suitable application had the capability to either minimize to the system tray or to the task bar based on a user setting with a sensible default. The close button should always close it (or if not, the behaviour should still be consistent across all applications).
I understand that some of my complaints are intended to be addressed already, so I look forward to my experience getting a little better, at least. I thank Matthew for the blog post - at least I know that these things are being worked on.
heh, this quote reminds me of one of the most fustrating things about osx, theres like 4 ways to hide a windows
1. minimise to dock 2. "close" but dont quit 3. hide 4. quit
I think I might be missing one as well, and they all work completely differently when you want to being the windows back.
The person with only one background service will see unnecessary cluttering with different kinds of menus. Take a look at the forums, a significantly large number of them ask about how to remove the messaging menu (because they dont use it)
In addition, I have a clipboard manager in the system-tray. Which menu does that come under ?
There seems to be a trend to making UIs less configurable and more "consistent" with the app designer's presumptions about how a UI should work. But does this justify sweeping away well-established UI conventions for something new and untested?
If you make the new UI a configurable option, one of three things will happen:
1. People will gradually discover the new UI option, try it out, and if it genuinely does improve their workflow, keep using it in the long term. In this scenario, your improvement will gradually displace the old convention, and you will eventually reach a point at which old convention can be retired.
2. Some people will adopt the new design, but many will continue to prefer the old convention. Here, there is no objective superiority of one solution to the other, and the best direction is to let it remain a configurable option.
3. Adoption of the new feature will be negligible. This might be because the established convention is in fact superior, but it might also be attributable to user simply having entrenched habits. Either way, it implies that the new solution does not have enough of an advantage over the old to overcome what users are accustomed to, and that the established convention is good enough. In this case, you should acknowledge that the change was unnecessary and revert back to the old convention.
This approach allows for UIs to evolve to suit actual usage preferences, and avoids the pitfalls of constantly changing everything in pursuit of an abstract and prescriptive notion of consistency.