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
