On Wed, Jun 24, 2015 at 10:17 PM, <m...@jtalk.me> wrote: > It's unwise to write an API without a working consumer. If you can't see > the whole set of tasks your application will need from your API you're > going to redesign your interfaces again and again. You should have started > from the Kopete messaging and GUI code falling to API once all your use > cases are clear. >
Hi, Thanks for your comment. > > I also totally agree with kaushik: write a simple core, extend it once > needed, write tests, then go to the next task. > I am now already working on the logger and search, then once it is complete I will move to the other tasks. > _______________________________________________ > kopete-devel mailing list > kopete-devel@kde.org > https://mail.kde.org/mailman/listinfo/kopete-devel > -- Thanks, Joshua
_______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
