| Summary: | Wish: Improve KDE, be less obtrusive! | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Niels van Mourik <niels> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Bugs.kde.org is a bug tracker, not a forum. The issues you mentioned here are all covered by other bug reports. You even commented on some of them. Closing this report : One issue = one bug report. |
Hi there, As a wintered programmer the first thing - besides stating that I don't have enough time myself - I would like to state is how much of a beautiful piece of tech Akonadi actually is. It's architecture makes total sense, the system works and came a very long way but is getting rock solid. The point I would like to make to everybody is that Akonadi is a background service that never facilitates users directly, it facilitates developers of front-end implementations like Kmail and Korganizer. Although I'm not telling any new here, where I do want to emphasize on is Akonadi's role in the user interface of the average KDE user ("John Ko" :p). The fact the project has a logo and is named generically "PIM services" in some dialogues is good and there's nothing wrong with that. However, there are several examples in it's design where we wouldn't want the user to be bothered with things - most users - won't understand initially, let me give some examples: - Not automatically going back to online mode after connection failure (kmail). - Failed connection notifications, technical error messages that disturb users. - Conflict notification that disturb users instead of forced automatic conflict resolution. - Presence of the systray applet named "AkonadiTray", why no generic naming? - Any direct mentioning of "Akonadi" where users expect something they understand. - Akonadi not automatically shutting down when it's not needed anymore, saving resources. Well I gave some examples and I do know and realize that many tickets created probably try to mention them or users giving their irritation on it. My point here is a little bit different though. Once we are at the point that the average user never sees Akonadi or knows about its existence anymore we have accomplished something very useful, a KDE experience that "just works " (TM) with rock solid PIM service integration everywhere. I genuinely think that getting more user expected behavior in the interface bits will improve the product and thus the long-term satisfaction for the limited resources behind Akonadi! When I ever find the time I will try to work on bits like the ones mentioned! Thanks a lot for listening to my plea! Niels