APR
6
2011

KDE 5 Menu

Note in bold: no official plans here, however many continuously maintained software projects start with N+1 version development long before N version is discontinued. So yes, I really think the current works at UX level are "the" KDE 5 development.

Transition to KDE 5, whatever it means, is a process not just one atomic step. Today a follow up of the previous entry about fruits of the Calligra Sprint: Modern "File" menu merged with start-up view.

The need

The ideas were much older but it all started to take shape in January 2011. First, some analysis and mockups born.



While the mockups are prepared for document-oriented app, namely Calligra Words, the aim was to have something fitting for specialized apps like Kexi, where document is not the center of the application's work flow. You know such apps do exist, and you probably use them. Think of KDevelop as a notable example from the KDE world, and Eclipse or Qt Creator from another. For such apps it is typical that so-called Project is the center of the work flow, not a document, and there are multiple views (at least 5 in Kexi now, and 3 in KDevelop). Thus, the Project is term referred by the menu otherwise called "File" menu.

It is important to say that the topics covered here do not include the "Tabbed Toolbar" menu. Interestingly, the modern file menu concept is compatible both with the current classic menu bar used by document-oriented Calligra applications and with the "Tabbed Toolbar" menu used in Kexi 2.

All these notes show that talking about KDE 5 make some sense. We see increasingly more ideas like QML reuse and going with simplified UIs. Now there's more freedom of expression than ever. The target platforms differ each other more than ever, and the user base is diverse: something what needs to be addressed.


One of the mockups: Page displayed when user clicked "New..." command in Words.

The implementation

Within Calligra, the app that would benefit most from the flexible start-up and "File" menu is Kexi, so I proceeded with initial implementation for this app specifically. This means that the special "Kexi" button is merged with the Tabbed Toolbar rather than the conventional Qt menu bars.


Watch on YouTube
(see also MPEG file)

One of the important differences between the ordinary QMenu with actions and the newly developed is that the latter uses no modal windows at all (instead it includes these windows as views) and itself it is not a popup. This way the user experience becomes closer to browser's UX. And by definition, less mouse clicks are needed.

Technically the main challenge was to force QMenu to be ordinary child QWidget. The original QMenu forces to be a separate window of popup style. I wanted the new menu to have mostly the same API as QMenu to reuse as much the KAction features as possible. At the moment it was not possible without a fork of qmenu.cpp (note: feel free to invest your time into improving it e.g. at Qt level, then I am here to help, otherwise any requests will not be very effective :) ).

Besides reusing of the the QMenu API, the main assumption also was to maintain the features like Accessibility, Right-to-Left, and have QStyle-independent solution (that would be hard without QStyle proxies).

The code is available in the Calligra repository, kexi-modern_menu-staniek branch. It is not yet clear if it makes its way to Calligra 2.4 or 3.0.

What we already have: the menu with so-called persistent selections, a place for displaying "views" like Templates List, and the "Kexi" button. Compared to the mockups we lack the search box (upper-right corner), which is independent task, and only the "New project" page is integrated.

In addition the Tabbed Toolbar has been uncluttered by removing extra lines from the QTabWidget-based implementation (again, largely thanks to the QStyle proxy). You can compare the effect by looking at the movie and Kexi's 2.3 menu.

Wrap up

Final reminder: Ideas are rarely 100% original, and art is built on stealing. But developments presented here are continuation of earlier works, not a cloning of some recent software. I recommend reading this post from 2006.

I demonstrated the working results at the Calligra Sprint. I was especially interested how the mockups were received at usability level; Anna-Lisa mentioned the modern menu idea (mockups) was received mostly well among the users taking part of her usability tests. Now it will be possible to also test the real interface and improve it.

Next time I will write about Qt-only strategy for some Calligra library code.

PS: Would you like to join us, the Kexi Project? Do not be shy, write to [email protected] and start today :)

Comments

Cool stuff for Calligra ;)

But, Keep in mind this (i think) do not works for normal apps... A single menu button (in kwin) with a simplified menu is the way to go.


By Cédric Bellegarde at Thu, 04/07/2011 - 06:46

(Single) Menu in KWin is not way to go anywhere as it does not work with other window managers and it does not work well with touch screens or mouse/keyboard controlled computer. It does not follow usability guidelines or it is not even possible to configure as the current menu structure.

I dont like this menu neither as it seems so badly cluttered and hidden that every function need to be searched and mouse cursor need to be moved more than with drop-down menus.


By fri13 at Thu, 04/07/2011 - 18:02

If you try it you will see there's less mouse moves not more. This was the goal. The new menu also has less items than the traditional menu and the items are easier to spot (you seem to be interested in touch interfaces). So there is less clutter, more structure. The contents of the that 'views' are displayed inline near the menu items, what also often translates to less mouse moves compared to dialogs. For example with traditional menus+dialogs, in order to browse through the interface, user needs to close the opened modal dialog, get back to the menu, scroll down to select different action.

I agree with the KWin note, it's not clearly universal, however apps can optimize themselves for KWin-based UIs and "degrade" elsewhere. I've seen worse attempts (because per app) to simplify the interfaces, e.g. Google Chrome's completely custom window.


By Jarosław Staniek at Thu, 04/07/2011 - 22:28