Skip navigation.

Evolution 2.0 UI proposal

Evolution
Evolution

Here at Ximian we have been brainstorming a bit about what happens
next in the Evolution world. One of the ideas that has come up is a
substantial overhaul of Evolution's UI.

Since images speak better than words, here are the mockups for some
designs that Anna has developed: (this is just to give a very rough
idea of what it would be like; the icons and labels are not final, the
widgets are not the real ones etc.)

Read the rest

Re: Evolution 2.0 UI proposal

I definitely agree! This drives me nuts as well. I hate having to use the preview pane to navigate through messages in a folder, and double-clicking on each message to view it in a separate window and then clicking again to close it is grossly inefficient.

I wasn't even *aware* that there were keyboard shortcuts for unread-message navigation, since these keys are not found in any message-window menus, which is really bad UI design. Unless the user reads the manual, there is no way of discovering these shortcuts except by accident. I hope this gets fixed in the next version of Evo.

In any case, I agree with you that it should be possible to navigate through *all* the messages in a folder, not just those that are unread. However, since both types of navigation are sometimes useful, perhaps there should be separate pairs of keyboard shortcuts for each type of navigation --

Perhaps , & . should be used for unread messages, and [ & ] should be for all messages. This would eliminate the needless redundancy in the current key mapping, and add a very useful feature. If these shortcuts are available, they must also be discoverable through a menu *in the message window*, and not just in the main window. There should be a Go-To submenu in the Actions menu that lists all of these shortcuts, so people don't need to guess. It seems to me that any keyboard shortcut that is available in a window should also be available from that menu's window, and this requirement should be specified in the HIG if it isn't already.

I'll have to see about filing bugs about some of this stuff...