Language Selection

English French German Italian Portuguese Spanish

KDE 4.4 Mail Misunderstanding Explained & Akregator Surprize

Filed under
Linux

I've gotten quite a few responses to my quickie look at KDE 4.4 under Mandriva written for this week's Distrowatch Weekly. One of which came from Aaron J. Seigo himself. I thought I might share some of what he said since several people expressed similar concerns on the topic here in comments. I also found one really super-duper neato new feature in Akegator in 4.4 that deserves a mention.

First to all, that wasn't meant to be a thorough review of KDE 4.4. I just wanted to talk about how easy it was to upgrade Mandriva and to install the KDE 4.4 packages and perhaps mention a few observations.

But one concern that several people besides myself have mentioned about KDE 4.4 PIM here on Tuxmachines was our understanding that our emails used in KDE PIM will be converted from our maildir format to database entries. This would make testing various distributions a bit more difficult. I know a little MySQL, but I really didn't want to be dumping and restoring a database every time I changed distributions.

But Seigo explains that our mail will not be converted and stored in a database. An index of our mail will be made and stored in a database table so that other applications could make use of it. Apparently, allowing for opening and accessing the mail in its current directory and format if need be - for example, as in a plasma widget on desktop monitoring for new mails. At least that's how I understood his explanation.

Well, instead of interpreting, I'm sure it would be alright to just post his exact words:

Actually, Akonadi doesn't change storage format (that wouldn't be a good move, really) but it centralizes access to the storage as well as provides uniform indexing. Right now, indexing systems aren't shared between mail/calendar/contact systems anyways, and Nepomuk allows the indexing to be shared between all desktop apps that use it. Akonadi itself provides access to the mails on disk so that it's safe for both, say, KMail and and a Plasma widget to be displaying the contents of the at the same time. So instead of being a heavy or "lock-in" style database, it's simply an access mechanism to storage formats that you and I are already (and will continue to) use.

I know this takes a load off my mind as I hope it does the others who expressed concern as well.

---

Now for the super-duper neato new feature in Akregator:

Akregator used to display polls and such as plain text, but with 4.3.2 polls rendered in radio-button or clickable format. That was kinda nice. But today I discovered something even better.

For Webmasters/bloggers/whoever that allow such, videos can now be watched right from Akregator. I don't know any real details, if only certain formats are supported and such, but I'm almost thinking they'd have to be oggs. I'm not sure if Flash videos would work as I disable all such in Konqueror/KDE. I'll check next time I see where someone embeds one in a feed.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: akonadi problems

On my experimental box, I'm running Mandriva's development version called Cooker (currently in Alpha state). When Cooker KDE packages were updated to KDE 4.40, akonadi wouldn't load, so kmail would terminate. Irritating. Started looking on the net, and in logs. Turned out the akonadi MySQL database config was incompatible with the MySQL packages in Cooker.

Some small changes in the akonadi mysql config file got it working.

Oh well, such is the life with alpha stuff.

Wish KDE would allow kmail to run without akonadi, for the time being.

re: akonadi problems

oh no. Another issue to be wary of. That won't be the only occurrence of similar in the coming months I'm afraid.

Yes, there should be some choice in the matter. A lot of folks would rather not have to have a database installed on their desktop.

Issues of space, resources, unknown future of mysql... that database indexing should be an option one can opt out of.

More in Tux Machines

today's leftovers

Software: VirtualBox, TeX Live Cockpit, Mailspring, Qt, Projects, and Maintainers

  • VirtualBox 5.2.2 Brings Linux 4.14 Fixes, HiDPI UI Improvements
    The Oracle developers behind VM VirtualBox have released a new maintenance build in the VirtualBox 5.2 series that is a bit more exciting than their usual point releases.
  • TeX Live Cockpit
    I have been working quite some time on a new front end for the TeX Live Manager tlmgr. Early versions have leaked into TeX Live, but the last month or two has seen many changes in tlmgr itself, in particular support for JSON output. These changes were mostly driven by the need (or ease) of the new frontend: TLCockpit.
  • Mailspring – A New Open Source Cross-Platform Email Client
    Mailspring is a fork of the now discontinued Nylas Mail client. It does, however, offer a much better performance, and is built with a native C++ sync engine instead of JavaScript. According to the development team, the company is sunsetting further development of Mailspring. Mailspring offers virtually all the best features housed in Nylas Mail, and thanks to its native C++ sync engine it uses fewer dependencies which results in less lag and a reduction in RAM usage by 50% compared to Nylas Mail.
  • Removing Qt 4 from Debian testing (aka Buster): some statistics
    We started filing bugs around September 9. That means roughly 11 weeks, which gives us around 8 packages fixed a week, aka 1.14 packages per day. Not bad at all!
  • Products Over Projects
    However, projects are not the only way of funding and organizing software development. For instance, many companies that sell software as a product or a service do not fund or organize their core product/platform development in the form of projects. Instead, they run product development and support using near-permanent teams for as long as the product is sold in the market. The budget may vary year on year but it is generally sufficient to fund a durable, core development organization continuously for the life of the product. Teams are funded to work on a particular business problem or offering over a period of time; with the nature work being defined by a business problem to address rather than a set of functions to deliver. We call this way of working as “product-mode” and assert that it is not necessary to be building a software product in order to fund and organize software development like this.
  • Why we never thank open source maintainers

    It is true that some of you guys can build a tool in a hackathon, but maintaining a project is a lot more difficult than building a project. Most of the time they are not writing code, but [...]

today's howtos

Tizen News