Re:API for history plugin

[email protected]
Newsgroups gmane.comp.kde.devel.kopete
Message-ID <[email protected]> 
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.

I also totally agree with kaushik: write a simple core, extend it once needed, write tests, then go to the next task.
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.