open-slx end-user platform announced

A couple of months ago at open-slx, when we (like so many times before and after) talked about how we can make the lives of Linux users easier, an idea was sparked. While there’s huge amounts of content out there, it struck us that there’s still a large number of people not being too well served when searching Google to get answers to your questions. This poses some problems though: First of all, most of the information is not in English. This poses an extra barrier for some, who might not be as fluent in English as we developers usually are. Then, the content is hard to verify: How do I *know* that the information given there makes sense? Maybe it will just delete all my erotic movies? ;) So the problem is that there’s little content for the German end-user audience, which is hard to verify. So a team consisting of openSUSE community members and open-slx employees led by my colleague Rupert Horstkötter has set out to fix this problem. They looked into existing solutions to these problem, and found that what is currently running as ubuntuusers.de comes closest to the solution we have in mind. We got in contact with the team at ubuntuusers.de, and they were enthusiastic about the idea and willing to make it happen. A good start.

Then comes the real work of course. We’ve worked out a concept that allows us to provide a modern support tool for our users, which builds on two pillars: information and interaction. The concept we come up with puts this into three different tools: a wiki as knowledgebase, a forum to discuss articles, questions and to get in contact with other people, and a blog aggregation (Planet) which collects news about developments in openSUSE and howtos for specific topics. In order to accomplish this gargantuan task, we’ve asked for help in the openSUSE community. People were immediately enthusiastic about the idea, and started chipping in, helping to review and improve lots of articles.

Over the past few months, we have reviewed about 2000 articles from the existing ubuntuusers.de knowledgebase, prioritizing 500 of them, and adapted the articles to modern standards and that they apply to openSUSE. These 500 articles form the foundation for the knowledgebase we created for the open-slx community platform. We’ve also set up a webforum users can use to communicate and ask further questions, and we’ve put up a blog aggregator.

So, if you’re a German-speaking user (or future user :)) of openSUSE, hop over to community.open-slx.de and see for yourself whether this new platform fits your needs (and if it doesn’t, let us know what we can improve). You can find the official announcement here.

Solides 4.6: Neuerungen in der KDE Hardwareverwaltung

In KDE Plasma 4.6, dass im Januar erscheinen wird, sind so einige Sachen, die den Bereich Hardwaremanagement verbessern. In diesem kurzen Artikel highlighte ich zwei davon: Netzwerk und Powermanagement.

Energieverwaltung

Netzwerkkarten Details im Networkmanager PlasmoidHier haben die meisten Änderungen unter der Haube stattgefunden. KDE’s Hardware Abstraktionsschicht Solid kommt jetzt gänzlich ohne HAL aus und baut auf die U* Familie, die aus UDev, UPower und UDisks besteht. Eine Änderung in Solid ist, dass jetzt mehrere Backends gleichzeitig ihre Arbeit machen können, was auch notwendig ist, da das monolithische HAL durch die modulareren U* Komponenten ersetzt wurde. Für Applikationsentwickler ändert sich allerdings nichts, alle Solid Funktionen funktionieren nach wie vor, nur benutzen jetzt im Hintergrund einen anderen Mechanismus um ihre Arbeit zu machen.

Eine weitere Änderung hat das Solid Team in mit PowerDevil2 eingeführt. PowerDevil ist ein kleiner Daemon (eigentlich ein Plugin für den KDED) der verschiedene Energiesparfunktionen bereitstellt, wie z.B. das Suspenden der Maschine und Energiesparprofile. PowerDevil2, der in 4.6 neu ist, ist modular aufgebaut und kann mit eigenen Aktionen erweitert werden. So können Benutzer das Verhalten der Energiesparfunktionen komplett selber bestimmen, und sind nicht mehr von hardcodierten Funktionen die mitgeliefert werden abhängig. Diese Action Plugins integrieren sich nahtlos in die Profileinstellungen, wie man auf dem Screenshot sehen kann. Das Batterie Plasmoid, über das auch andere Energieverwaltungsfunktionen, wie z.B. Suspend und Hibernate verfügbar sind glänzt im 4.6 Releasezyklus vor allem durch Bugfixes. So habe ich diese Woche noch 4 Patches, die Aurelien bereits in den Trunk Zweig eingeplegt hatte auf das bereits abgezweigte 4.6 Branch zurückportiert.

Für 4.7 plane ich, erweiterte Informationen über den Energieverbrauch und Zustand der Akku(s) hinzuzufügen, ich habe mit der Entwicklung davon bereits begonnen. Dazu allerdings mehr zu einem späteren Zeitpunkt, jetzt liegt erstmal der Fokus auf Plasma 4.6, und danach darauf, das openSUSE 11.4 Release rund zu gestalten.

Netzwerkverwaltung

Energieverwaltungs EinstellungenopenSUSE liefert im 11.4 Release, das auf KDE 4.6 aufbaut das neue Netzwerk Management Widget mit, ein Plasmoid dass es erlaubt Netzwerkverbindungen aufzubauen. Im Hintergrund baut es dabei auf den bekannten NetworkManager auf. Um die Jahreswende sind hier vor allem noch VPN Funktionen hinzugekommen, dank einiger freundlicher Entwickler, die mir Patches zusandten. (Ich selber benutze kein VPN, bin daher auch auf die Mitarbeit anderer angewiesen.)
Ansonsten unterstützt das neue Applet Wifi und Ethernetverbindungen sehr gut, ist aber auch für’s mobile Internet bereits gerüstet. Die Integration des Modemmanagers ist bereits weit fortgeschritten, und sollte funktionieren. (Auch hier kann ich’s nicht selber testen, falls es hakt bitte Bugreports einstellen. Wer drahtlose Netzwerke benutzt, die ihre SSID nicht broadcasten, d.h. die "unsichtbar" sind, hat im Moment leider noch Pech, die Unterstützung für diese Netzwerke ist noch nicht komplett. Man kann sich aber behelfen, indem man (als root) "iwlist wlan0 scanning essid <MYSSID>" ausführt. Danach ist das Netzwerk in Plasma sichtbar, und man kann sich damit verbinden. (Dieser Vorgang ist nur einmal nötig, da das Netz nun in Zukunft direkt erkannt wird.) Visuell bin ich mit dem Netzwerkeinstellungsplasmoid schon recht zufrieden, d.h. im Grossen und Ganzen tut es das, was es sollte. Es gibt noch einige Sachen, die ich kurzfristig beheben möchte, so kann es vorkommen, dass die Liste auf der rechten Seite leer ist, d.h. keine vorkonfigurierten Verbindungen zur Verfügung stehen. In dem Falle sollte man drahtlose Netzwerke in der Nähe sehen. Meinerseits liegt der Fokus hier also vor allem auf Polishing und Bugfixing, sodass es nicht nur cool aussieht, sondern auch so reibungslos und unauffällig wie möglich funktioniert. Es sind allerdings auch nette Features wie Unterstützungen für "system connections", die dann auch aktiv bleiben, wenn man ausloggt.

Running for the openSUSE Board.

I’ve just sent off an email, in which I’m announcing my availability as candidate for the openSUSE board, which will be elected in early 2011. Here’s what I wrote:

Hey openSUSE community, valued election committee,

Following up on the call for candidates, I’d like to let you know that I’m intending to run for the openSUSE Board.

In my dayjob, I am responsible for user experience at open-slx, and will be able to invest time on a regular basis into participating in the openSUSE board. I have a degree in business science, which gives me some formal insight into organisational processes, this has helped my work for the KDE e.V. in the past, and it will surely be benefitial for openSUSE. I am 34 years old, and live in Nijmegen, in the east of the Netherlands.

I have more than 4 years of experience in administering a Free software project (I’m member of the KDE e.V. board since 2006), and during this period have helped turning the KDE e.V. into an effective community representation and supporting organisation, which in many ways acts as a role model to other, similar organisations. The Geeko in me is about 9 years old, it started with openSUSE 7.2, which got me hooked on Linux. After a period of trying all kinds of Linuxen, I’m firmly back to openSUSE for about two years now.

openSUSE represents to me a technically excellent product with a friendly, helpful and skilled community around it that is failing to realise its potential, and in many ways is searching for orientation and a clear mission. Aside from organisational topics, this process I’d like to facilitate.

My platform for the elections is to help set up the openSUSE e.V. (or rather a legal representation of the community, as outlined in the current plans), and to help the community through the process of becoming more independent from Novell, which in my opinion is important for the growth and sustainability of openSUSE as product and community. I’m a Free software dude by heart, and the principle and ethics of the Free software community will be what drives my decisions as executive. My experience as "cat-herder" will be beneficial in the same way.

I do realise that my involvement in the openSUSE community has been fairly transparant, following things from the sideline, stepping in actively here and there, and certainly far from taking on any role as rock-star. I am planning to further ramp up my profile, since that a) will make the members’ decision during the elections a lot easier, and b) it improves accessibility and visibility of the TOTRoS (The Organisation That Represents openSUSE).

This email is just to let you know in advance that I’m intending to run for the board. As I /also/ intend to go on vacation on Friday, I might appear unresponsive until ~christmas. Still, I opted for letting everybody know early on that I’m intending to run (rather than sending my note of intent to run after christmas), as planning will likely make the work of the election committee a bit easier.

Surely, if you’ve questions already, feel free to ask. I will, after returning from vacation be more outgoing about my involvement with openSUSE and my ideas and plans for the openSUSE board.

Thanks for your attention, and your support.

*jumps off the soapbox*

Cheers,

—

sebas

we are out of househacking & KDE e.V. Board Meeting in Nijmegen

I’ve just returned from our local microbrewery, Brouwerij de Hemel in Nijmegen, the Netherlands, the place where I live after a nice dinner with my fellow KDE e.V. Board Member members. Friday and Saturday we had planned to hold a two+ day board meeting here in Nijmegen. Kim and me have moved into our new house in Nijmegen two weeks ago and we’re now mostly settled, meaning all critical parts of infrastructure work and are in place, and we can pick up our lives again, after two months of updating, maintaining and facelifting it from the inside. We’re now fully settled. We’ve moved inside Nijmegen from a rather nice flat into a larger house. We got the keys to the new house two months ago, and have spent this year’s september and october on painting, wallpapering, insulating and other facelift and maintainance work. Luckily, many of our friends and families came by to help us here and there. The whole process went pretty well overall, and we stayed inside our budget aswell with a result that’s really a nice improvement in terms of quality of life at home. Part of the renovation work in the new house was upgrading the attic, which was mostly used as storage space to a modern relaxed working environment. As I work from home, effectively I’ve moved office and home at the same time. The attic is now nothing short of a humongous home office, housing my large corner-desk with the dual-screen workstation I use for daily work at home, a sofa, "relatively neatly" organized cables (we all hate this mess, don’t we?!), a cool new TV with internet and UPnP snazziness, hifi system hooked up to computer and TV, a nice couch, air-conditioning, large windows, WII, etc. The roof got a 8cm insulation layer as well, so the house is much less of a climate waster now that we applied some TLC (blood, sweat, no tears) to it. One the one hand I feel like the small boy again being all happy and impressed by all the new toys, but on the other hand I’m already experiencing in my first two weeks of work in the new office that it’s exactly what tickles me to be productive and relaxed at the same time — I love it when a plan comes together.

One of the factors I’ve considered for the new office is the lighting. I’ve chosen three differently placed sources of light: 4 built-in spots above the desk, three spots under the rooltop, and two small diffuse table lamps in the lower corners. They’re separately dimmable using a small remote control, so it’s easy to adjust the lighting in the room conveniently from either desk, or couch. I’ve used halogen lamps for all lamps, after playing around with different options. There are energy-saving lamps, even the supposedly dimmable ones don’t work really well when combined in different settings. I’ve tried three different products from different vendors, and they were all not working well, meaning flickering, inconsistent switching, delays in lighting up. Even the more expensive ones (supposedly dimmable) are basically unreliable and annoying. In our bed room, I’ve installed LED lamps in a 3-spot lamp. The first set of LED lamps I’ve tried for it worked well (no dimmer involved), but the light was abit on the "cold" side. It looked a bit too slick for a bed room. I’ve replaced the lamps with similar lamps in 2700Kelvin (the ‘colder’ ones were 3000Kelvin) and the light is certainly comparable to Halogen light. The downside here is that the lamps are really expensive (~40€ a piece). They’re supposedly dimmable, but I haven’t tried that yet. The halogen light that I ended up installing in most places (either as lightbulb with inner halogen lamp, or as spots) gives the perfect, most stable and well-toned light, and dimms perfectly with very low thresholds on the dark side and really bright light when turned up. Halogen lamps are comparably inexpensive, but they not exactly energy-effective (only save about 30% compared to traditional lightbulbs, whereas you can easily save 70% by using LED lamps. The trade-off will likely go towards LED lighting in the near future, as the technology matures, R&D costs are being earnt back and economies of scale make LED lamps more affordable.

In the preliminary end (last monday-ish) the house was ready for its quite unusual inception and first stress-test: KDE e.V.’s fall board meeting.

KDE e.V. Board Meeting

Celeste Lyn Paul arrived on Thursday morning from Washington DC, Adriaan de Groot (fellow Nijmegenaar and e.V. vice president, Frank Karlitschek and Claudia Rauch, KDE e.V.’s business manager attended respectively spoke at the Netherland’s UNIX User Group’s semi-annually conference. After letting Celeste in and quickly showing her where she can find what she needs (quite easy: shower, place to take a nap, possibly food / coffee, etc.) I headed out to a meeting at the NLUUG conference in Ede where we looked into funding opportunities for KDE developers. Interesting stuff, of which I hope we can materialize some in the coming months. After getting back to Nijmegen, Celeste and me picked up Cornelius who arrived at the train station, and we went for dinner in the oldest bar in Nijmegen, De Blaauwe Hand. Tapas-style food and some bok beer really kicked off the board meeting. The weather solidly sucked with rain and wind, which is very expectable on the one hand and provides big grins on the other hand when explaining that trains are delayed because the wet rails are slippery (seriously, wtf).

The next morning, after a rather "warm" welcome the night before, we started planning the meeting. Usually, we prepare the agenda before the meeting, this time we decided to be a bit flexible there and decide about the agenda at the beginning of the meeting. I don’t think it made a big difference in the end, so in the future I’d probably lean towards prep’ing the agenda before the meeting on the mailing list, to save some valuable face-time for less administrative tasks. The board meeting was otherwise pretty productive. It struck me that the load of administrivia to deal with was rather bearable, which reflects well on the work we’ve done over the past years consolidating our operations. "Consolidating our operations" of course means "Claudia and her team in the Berlin office (currently Agata and Jenny, previously Torsten) take board member’s headache away. :-)

The fact that the KDE e.V. is a well-working, stable and effective organisation is quite convenient as it allows us to be more out-going, and more "enabling" as an organisation. While we have increased our investments in things like developer sprints, Akademy, travel support for KDE developers, promotion and many other organisational things, we have also been able to increase the income alongside: both sides of the balance are in healthy ratio. As we’ve planned quite conservatively financially over the past year, we even have some financial space to tackle bigger ideas. One idea of Cornelius I really liked, but it’s just too awesome to share at this pristine point, so I’d rather disappoint my readers here. Stay tuned, anyway. :P

I’m really proud to have contributed in this rather special way, by hosting my fellow board members here. We’ve had lots of good meeting hours, but also some very valuable face-time. Kim was rather helpful in the background, so that’s where the credit for the host should really go. So much for Nijmegen. Tomorrow, Frank and I will be doing some hacking here, and then flying off to Dublin for the MeeGo conference. In short: after having taken some more time for personal stuff, I’m back in full swing. Arrrrr.

Moving.

Just a quick shout-out, K, me and the pets (and computers) are moving into the new house now, which means I’ll be hard to reach over the next couple of days. I should be fully moved into my new home office on Monday. Progress can be monitored here.

See you on the flip side. :-)

Schizophrenic clock effect

On the train back from the openSUSE conference, I read an article about improvements in Plasma 4.5 in the German edition of Linux Magazin. The author noticed the re-designed notification area with its more consistent and clean look, but also mentioned that the clock looks visually somewhat outdated in the panel now. Fair enough, most of the notification area has seen a bunch of iterations over their looks, but the digital clock didn’t really receive much visual love other than bugfixes in alignment and layout of the clock. I thought a bit about what would make the digital clock look better, and identified two things: the full bleed color sticks out a bit, and the clock looks flat compared to its neighbours in the panel.

Touching up Plasma's digital clockAfter a couple of iterations and with feedback from some Plasma (and non-Plasma people) I have just committed to Plasma trunk what I think is a good-looking solution, and a touch-up of the panel, making the whole look more belonging to each other. As you can see in the comparing screenshots, it also works well with a dark theme, such as Oxygen. What I did is the following: First, there’s a backdrop behind the clock’s text display now, in the background color defined in the Plasma theme. On light themes, such as the Air theme, this produced an emboss effect, making the time appear slightly sunken into the panel. On dark themes, the backdrop is dark, and hence looks like a shadow, so the time seems slightly elevated. This difference in appearance has to do with how the human brain interprets dark and light colors. Wired has an interesting article giving some background on this — it appears that schizophrenic people’s brains interpret this in a different way.

Clock with new effect on the desktopSecond, the time is now also displayed with a translucent gradient in the text and has a very subtle appearance of a lighting source, making it looks less flat and a tad more natural. The translucency gradient makes the time stick out a bit less, while still having enough contrast to be able to read it. The effect is a bit more clearly visible in a bigger clock, so here’s another screenshot of that. Thanks to Fredrik Höglund for this nice idea and the pointers how to do it. (You define a gradient a QLinearGradient, create a QBrush using this gradient, then you can instantiate a QPen using this gradient brush, and use this pen to paint the text.)

This might look like a small improvement, it’s nevertheless time well spent. The clock takes space on everybody’s screen, most of the time, so it should well be doing its job in an elegant way.

openSUSE conference 2010

These October days, I’m spending in Nürnberg in Southern Germany to attend the openSUSE conference. My role here is three-fold, first and foremost I am here as a representative of open-slx, my employer who sells products and services based on top of openSUSE. Then, I’m a KDE ambassador. Finally, I’m also getting more and more involved with the openSUSE team, getting to know many people and learning about challenges and opportunities this community faces.

That last one is actually really interesting, as the openSUSE community is in the process of re-finding itself. There’s the discussion about strategy going on, which is I think mainly formalizing the biggest problem openSUSE has: It’s lacking a common direction. This is a symptom of good and bad things, it reflects the diversity in the openSUSE community, which I think is of great value. On the other hand, it makes it hard to deliver one coherent product as there are nearly as many goals and opinions how to reach these goals as there are people in openSUSE.

Another part of this process is the de-coupling of the openSUSE community from Novell. This independence is very important for the Free software community since it means taking your own decisions — for instance about the direction of the product. Now my impression is that Novell doesn’t want to abandon openSUSE, but it’s trying to make it stronger by giving it more independence, it’s some sort of growing up of openSUSE.

Yesterday, I attended a session about setting up a foundation for openSUSE that can manage funding, governmental aspects and other more organisational tasks. Interestingly, the openSUSE board has (after looking at many comparable organisations in the Free software space) taken a direction very similar to how KDE with the KDE e.V. backing it up is set up. This is good to hear, since on one hand it validates the work we’re doing in the KDE e.V., and it’s yet another way of sharing in the Free software ecosystem. (Actually, we get requests for organisational assistance from Free software or Free culture projects on a somewhat regular basis.)

I’ve just attended a talk by Cornelius and Vincent (KDE resp. GNOME) who were talking about freedom in the cloud, giving a nice overview how the values of Free software apply to application used from the cloud. The rest of the day is packed with technical sessions, which I’m really looking forward to, and towards the end of today, I’ll talk about user experience in openSUSE. Actually, I’ve decided to talk about user experience and interaction design in general, explaining typical design processes and tools. I aimed for a talk teaching and explaining techniques this time around, since I think that this applies best to a community from kernel hackers to UI designers. My hope is that people will take away some ideas of how to improve the user experience of their work.

Solid Sprint Photo Blog

Sleep deprived as I am, I figured I’d do something more visual than my usual wall of text (quoting TGEN: "tl;dr", or for the markeys and others blessed with attention deficits, like me right now after a bunch of really intensive days :-)). So here goes the Solid Photo Blog, fresh from Madrid:

Alex Fiestas (Ale-Ale-Jandroooo), BlueDevil hacker, UFOCoder and kind host of the Solid bunch

Alex Fiestas (Ale-Ale-Jandroooo), BlueDevil hacker, UFOCoder and kind host of the Solid bunch.

Categorizer, Bluetooth hacker, new KDE-UDev maintainer and KDE-ES Vice president Rafael

Categorizer, Bluetooth hacker, new KDE-UDev maintainer and KDE-ES Vice president Rafael "ereslibre" Fernando Lopez. UFOCoder and kind host.

Kevin

Kevin "ervin" Ottens: Solid Maintainer, Sprint Kanban Manager and my pillow-talk mate for the sprint (I spare you the details, but notice the ghost behind ervin).

The cutest youngest aspirant Solid hacker, branched off in Nuremberg.

The cutest youngest aspirant Solid hacker, branched off in Nuremberg.

Solid Sprint Group PhotoMandatory group photo, top-left to bottom-right: Dario Freddi (PowerDevil), Will Stephenson (Network Management, openSUSE), Kevin Ottens (Solid Maintainer, KDE Mobile platform dude), Lamarque Souza (Network Management mobile broadband dude), Javier Llorente (openSUSE dude), Alex Fiestas (Bluedevil, upower backend), Rafael "ereslibre" Fernando Lopez (KCategorizedItemView, BueDevil), Albert ‘tsdgeos’ Astrals Cid (KDE-ES presidente, localization expert), Sebastian Kügler (Power & Network Management (Plasma) chrome, KDE e.V. dude, me, myself and I). Background: Our Kanban-based workflow, containing tasks for internal communication and progress-tracking.

Agustin Benito Bethencourt, Gran Canaria Desktop Summit organizer, ASOLIF contact and generally nice 'high-level-thinking' dude

Agustin Benito Bethencourt, Gran Canaria Desktop Summit organizer, ASOLIF contact and generally nice ‘high-level-thinking’ dude. (Missing in the group-photo.)

Madrid's Gran Via, early morning

Madrid’s Gran Via, early morning.

Clearly a Power Devil.

Clearly a Power Devil.

Solid Kanban Wall, the tasks being worked on on sticky notes.

Solid Kanban Wall, the tasks being worked on on sticky notes.

Hackers hacking.

Hackers hacking.

It's a hacker, and it runs on water, man. ON WATER, MAAAN! (But not exclusively.)

It’s a hacker, and it runs on water, man. ON WATER, MAAAN! (But not exclusively.)

I’ve also uploaded these photos (and a bunch of others) to my FlickR pages, if you’re looking for the full-size versions or more photos, get them over there.

Plasma Photo Collage

ide Collage of random photos from my collectionToday while going through some parts of my photo collection, I’ve created a collage of some photos. It was actually more or less accidental since I was choosing photos to be printed and framed, but I couldn’t keep myself from arranging the photos nicely on my desktop. I’m using a dual screen setup on my desktop, and while browsing the photos on the left screen, I dragged the photos I’d evaluate for printing onto the other screen, creating Picture frame widgets displaying them when dropping the photos (this even works for remote files, pretty cool). The work-flow this way is actually pretty close to how I’d do it with real physical object, browsing through stacks of photos and putting a selection aside for further investigation.

The photos I happened to choose are taken in various parts of the world, there’s the old ship in Jamaica, the entry sign to Bora Bora in Brazil, Edinburgh’s castle, the entry hall of a spa in Budapest, a Spanish rooftop, Kevelaer’s basilique and of course a bunch of photos taken in Nijmegen, my home town — notably the perfectly boiled egg.

What kind of fun work-flows did you discover while using Plasma?

Getting Email Done: The Stack and the Heap of Lion Mail

In my previous article on this subject, I have introduced Akonadi as the personal information beehive on your computer, explained how it works, how it is designed and what the migration process to an Akonadi-based Kontact looks like. (openSUSE users should also take a look here.) In this article, I will dive into the workspace parts we’re introducing on top of Akonadi, notably the new email notifier system in Plasma – Lion Mail.
The Lion Mail email notifier is at its base your "you’ve got mail" icon in the panel. For users with more complex and high-traffic email habits, it offers a basic set of workflow tools to manage the daily stream of emails more efficiently and ergonomically. In this article, I’m describing some of the design concepts behind Lion Mail’s email notifier and its workflow features.

In the panel, you can quickly see if there are new emailsComplex email workflows are something I wanted Lion Mail to excel at. The idea is to make dealing with email as flexible as we can, so you can project your workflow onto it and have it make the daily flow of email more manageable, and less disturbing in the real work you want to get done. By default, the Lion Mail email notifier shows up in your panel when a new email arrived in your inbox, by clicking on it you can access the list of your latest unread emails in a small popup-window. The basic use-case is quickly checking if you’ve got new email. I will not dive too much into implementation details, as this article is all about work-flows and how it affects the user experience.

The idea is that, at all times you can see if there’s email to deal with. but not have it jump in your face. In order to be able to quickly dismiss something as "I’ll deal with that one later", or "ok, got it", there’s two queues in Lion Mail, the stack and the heap of Lion Mail.

The Stack — Incoming Emails

The popup shows a list of the new emailsThe stack is your incoming emails queue, it lists new emails in one or more folders. By default, that’s your inbox, but you can configure it to monitor any folders you like (yes, combining them from multiple folders is built-in). The incoming emails queue is a transient thing, it’s your stream of incoming emails, and the first time a new email gets your attention (but doesn’t shout for it). The stack allows you to dismiss new emails, or mark them as read or important. The idea is that new emails might fall into the following categories:

  • "Not right now" – A new email will get your attention later. You take notice of its existence now, but don’t have time right now to tend to it. It stays marked as unread, you’ll get back to it later.
  • "This I really have to deal with, later" — If you don’t respond to this email, the world implodes into dark matter, or your head gets torn off by zombie-chinchillas. You mark the email as important, for extra attention, you can leave it marked as unread.
  • "I am bored enough" — An email you deal with right away, either because it’s important or more interesting than what you’re currently doing, or maybe because it’s quicker to reply right now. In those cases, you open the email in your mail client to read it and possibly reply.
  • "OK" — You notice an email and know enough by peeking at it. It can drown in your inbox from here on, you mark it as read.
  • "v14gra on loan" – Something slipped the spam filters. You just want it gone. You hit the delete button and it won’t bother you again.

These are a couple of possible reactions to new emails. By offering the tools to deal with such situations at hand, in the context of these incoming emails, we can pre-sort the stream of mail while we receive it.

The Heap — Important Emails

Important emails are accessible in a separate listThis is where the heap comes in. The heap is an optional second list of emails you can show in the Lion Mail email notifier. It simply shows the important emails in your monitored folders. This way, it offers you a list of things you need to deal with, in essence your to-do list of emails. By putting them into a separate list, we have two overlapping categories of emails you want to deal with. Lion Mail can either display those important emails in a combined list, or using separate tabs for new and important emails. The latter is likely to appeal to David Allen fans, Lion Mail certainly is inspired by some of his ideas.

In the setup you can specify which folders to monitor and wether or not to show important emails

Email Items

The individual email items in the heap or stack offer a couple of options to open emails in your mail client, for marking emails as read and as important, and for deleting it. Needless to say that these buttons operate directly on the email, so the moment you mark an email in Lion Mail, it’ll change in KMail (or any other Akonadi-based email client) as well. When an email doesn’t satisfy the criteria for the heap of stack anymore, it fades out over a period of 5 seconds, so you get some "undo grace-time" if you clicked wrongly. The emails themselves show by default subject, sender, date and flags, you can expand to show some of the body as well. Email items employ a hover interface, when you move the mouse over an email, it reveals three controls as an overlay which offer flagging and trashing an email. Clicking on the icon opens the email in your mail client, you can also drag an email from these lists into your email client or Plasma workspace. I’ve chosen for a hover interface mainly for two reasons: less clicks and more discoverability. The emails don’t have a context menu right now, but there are a couple of useful options we could add there, for example forwarding or replying.

Emails can be sorted using flags directly from the popup

Excerpts — NLP people, listen up!

If someone comes up with a clever and useful implementation for email excerpts, I’m all open. Right now, I’m just showing the first couple of hundred characters in order to not blow the size of the widget beyond what’s reasonable in a small popup. As you can deduct, I’m not the most inspired mind in the world of language processing. In the UI, I’d rather avoid having to use scroll bars inside the expanded email body, as the list already might have scroll-bars. Nested scroll-bars will lead to annoying behaviour for mouse-wheel and flick-scrolling, so that should be avoided. The most elegant thing to do here is excerpting the interesting parts of the email, by skipping empty lines and possibly line-breaks, by removing reply-quoted parts, and so on. K9-Mail (a really good email client for Android) does this quite well, it’s often possible even from one line to judge an email’s content. We can easily fit 5 lines into the expanded email widget, and possibly even more, so I’d expect that with the right algorithm, we could do excellent there. If you’re into that kind of stuff, send me a piece of code that turns an email body (as QString, if you want) into a 200-300 character long excerpt, it should be LGPLed code and you’ll be properly credited. Sounds like a nice small, self-contained hacking project for a fall evening, no?

Otherwise, I wonder if "the other Sebastian"’s recent Nepomuk accomplishments in excerpting documents play into our collective hands, or we’re in his of course. :-)

Emails as first-class citizens in your workspace

There’s if course a lot more in the pipeline. In principle, Lion Mail can hold any email collection, existing folders, but also virtual collections, such as search folders or combinations of multiple folders. Lion Mail represents itself as an icon in the panel’s notification area, you can enable it in the notification area’s settings. It’s also possible to put Lion Mail widgets on the dashboard, desktop or netbook’s new page, you can of course add multiple Lion Mail applets holding different collections one one or different activities, and this way depending on what you are doing, think of showing your work’s inbox in your "work" activity, showing private emails in your "freetime" activity or showing neither in your hacking activity. In Lion Mail itself, that would be very easy to do, It’s built in mind with showing arbitrary sets of emails, the new email and important email queues are just specialized version of a generic email list.Email lists can be put on the desktop, and switched depending on your activity

Drag and drop is also one of the things that got a little bit of attention while developing Lion Mail. You can drag emails from Lion Mail into KMail for example to move or copy them to another folder. Plasma is also receptive to dropping mails (and in the future mail folders) onto the desktop. Lion Mail includes a Plasma widget showing an individual email. It can take different sizes, so you can either have a bunch of small emails floating around, or individual emails with full text on your desktop or dashboard for reference while working, as it often comes handy to have a related email available for a quick check if you’re looking into something.Single emails can be put on the desktop as well, for quick reference

Release plans and test-driving

In its current state, Lion Mail email notifier is already quite usable. The work to make it release-ready consists of completing some features, refreshing of monitored folders directly from the applet, and trashing emails. There’s also some smaller interaction glitches I’ll fix before it can make its way into Plasma cq. Kontact 4.6.0. There’s suspending removing items under your mouse (or finger) so you don’t accidentally click on the wrong email, some display funkiness here and there (spot the lack of space underneath emails in the screenshots), and the excerpts extraction I invited input to above. You’re already most welcome to try it and give feedback. It’s currently located in playground and will eventually move through the kdereview process into one of the released modules — I haven’t figured out which one would be the most suitable exactly. If you want to build it right now, I have to admit that it’s not completely trivial from scratch, as it requires kdelibs and kdepimlibs from trunk. If you have a reasonably recent 4.6 (trunk) snapshot installed, you should be good to go. Lion Mail does not offer the option to configure email accounts, you can do that from KMail2 or akonadiconsole.

Famous last words

The heap and the stack of Lion Mail offer the opportunity to create a more efficient workflow with your emails. By dealing with emails effectively as they come in, but without a context-switch to the full email application, it offers more workflow-based email management. The underlying idea behind Lion Mail is that emails become first-class object in your user experience, to integrate them as artifacts of your interesting information, rather than banning them into a monolithic application like traditional email clients. "Light-weight email work" can be done directly from the workspace, referencing emails in other tasks becomes a lot easier, the traditional email reader still serves as the work horse for most email reading (as opposed to noticing and referencing). Lion Mail provides the usual feature set in a more elegant and context-rich way. It is also heavily optimized for people with larger amounts of emails, and integration these streams of new and interesting emails deeper into the workflow of the user.