On Saturday 14 March 2015 11:54:18 Joshua Joseph wrote: > Hi Volker, > > On Thu, Mar 12, 2015 at 3:15 AM, <cyberb...@gmx.de> wrote: > > Hi, > > > > I think a database approach is better than xml storage. My > > improved plugin > > > > http://kde-apps.org/content/show.php/Improved+Kopete+ > > History+Plugin?content=154660 > > > > has noticable better speed for history search (I have big > > chat logs from many years + many protocols - about 40 MB), > > has improved import (for example duplicates: I used pidgin > > on windows, and imported regularly into kopete to have > > history all in one place). And I think it is better to not > > require to have the history in ram all the time. > > Yes database approach is certainly the best path to follow. I > think I can work with > the SQLite approach, combined with the current existing plugin > approach for backwards compatibility with old logs. Or would > it be better to have a tool to import the > old logs? >
In my opinion new plugin should read/store history only from new format. And it should support importing chat history from other formats (e.g. old/current kopete format, other IM formats...) and at first startup it should convert old/current kopete history to new format. It is because to have fast search/browse support for old chat history messages and combining history from more sources will be pain. If you choose SQL database approach, make sure you can handle problem with searching in HTML messages history. E.g make sure you will be able to search for text "message" also if it is html formatted as "mess<b>a</b>ge". -- Pali Rohár pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
