[Kde-pim] configuration in akonadi-next

[laurent Montel]

Le Thursday 18 December 2014 22:58:43 Sandro Knauß a écrit :
> Hey,
> 
> > > "Text" files are binary files with nice editors, that's all. (... just
> > > look
> > > at one with a hexeditor ;)
> > 
> > Haha. Very funny. No, not funny at all.
> > 
> > > Access, not format, is what matters.
> > 
> > Exactly. And that's why access with everybody's favorite console text
> > editor is important. Or even with sed, awk, grep, and friends.
> 
> +1. I love every file i can simply look into and do not have to use special
> tool to look at it. Also for bugreporters this matters: you can easily drop
> the content of a textfile and actually are sure that no passwords are
> transmited. Using a db you have to access the database, create a dbdump to
> have a readable thing.


+1 
Bug reported is indeed the good reason to have settings stored as plain text.

And indeed use a specific tools for it is totally evil.

Regards.

> But configuration should not be that heavy that any binary thing is needed
> to be fast. And the configuration is read at one time maybe triggered, when
> it was changed. So there is neither a timing issue nor a big chunck of
> data...
> 
> Regads,
> 
> sandro
> _______________________________________________
> KDE PIM mailing list kde-pim at kde.org
> https://mail.kde.org/mailman/listinfo/kde-pim
> KDE PIM home page at http://pim.kde.org/

-- 
Laurent Montel | laurent.montel at kdab.com | KDE/Qt Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53,  http://www.kdab.fr


_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/