Hi Joshua, Welcome to Kopete.
Understanding the existing plugin code and redesigning it will be the best way to go for it. However understanding the existing code will not be that easy. You will need some familiarity with these Kopete::Contact and Kopete::MetaContact. The logic inside HistoryLogger.cpp is not that difficult to understand. If you see huge methods, that is probably because it also contains the logic of parsing the history log ( which is read as QDomDocument ) and appending the incoming messages to it. Moving the logic to its own class or a different method will shrink the code and make it more readable. You can use a History object instead of the QDomDocument, or anything else you might want. Once you are a little familiar with the existing plugin code and If you need any help in understanding the logic, just ping us and we should be able to help. Thanks, Kaushik IRC - roide On 5 March 2015 at 13:07, Joshua Joseph <joejo...@gmail.com> wrote: > > > On Thu, Mar 5, 2015 at 10:01 PM, Pali Rohár <pali.ro...@gmail.com> wrote: > >> On Thursday 05 March 2015 19:37:38 m...@jtalk.me wrote: >> > > Also development of new plugin does not have to be from >> > > scratch. Maybe for somebody existing plugins could be good >> > > start point. >> > >> > I’m sure they will not. I took a look at their source code >> > earlier and it’s a >> > >> > complete mess. There’s literally one huge function containing >> > all the retrieval >> > >> > logic. The worst code I’ve ever seen outside of students labs, >> > really. I’ve spent >> > >> > about a week on refactoring and just gave up, and I’m a lead >> > C++ engineer, not >> > >> > a student. The only purpose of those existing plugins is to >> > know Kopete history >> > >> > API better as it’s not well-documented as far as I know. >> > >> > >> > -- >> > >> > Roman >> >> I understand you. But do not forget that new plugin must support >> converting old history files to new format = users must not lose >> existing chat history. And existing plugin is probably only one >> place where is code for parsing that format... >> >> > > I agree...to create backwards compatible software we'll have to look > at the old code, and create a better product. > > >> -- >> Pali Rohár >> pali.ro...@gmail.com >> > > > > -- > Thanks, > Joshua > > > _______________________________________________ > kopete-devel mailing list > kopete-devel@kde.org > https://mail.kde.org/mailman/listinfo/kopete-devel > >
_______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
