Re: API for history plugin
Joshua Joseph <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kopete |
|---|---|
| Message-ID | <CAKYNVbQA5wB-3zf7Rv2mK+Y6qt5nOkM1f9wwk+2tNtDAMwE0tQ@mail.gmail.com> |
On Wed, Jun 24, 2015 at 10:17 PM, <[email protected]> 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 > [email protected] > https://mail.kde.org/mailman/listinfo/kopete-devel > -- Thanks, Joshua _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel