这个文档路标不是一成不变的。他只是帮着我们关注所有任务的优先级。
Contents |
Storage abstraction is already in libkopete in SVN.
详见Kopete SVN中的IDENTITY_REFACTORY。
We should keep that point in mind when refactoring the contact list handling. Some tasks could really use this pattern, like deleting a contact. Currently there is no way to be notified if the deletion of a contact went wrong. Most of the contacts tasks are implemented as methods of some classes, like Kopete::Contact::deleteContact which return.....void.
Using the Command pattern allow us to use signals for notification and encapsulate tasks into proper objects. One task, one object. Easier to maintain too.
Kross是KDE4的一个脚本引擎,增强应用程序中的脚本支持。支持多种脚本,如Python, Ruby和JavaScript(ECMAscript)。用脚本写插件将是件令人震奋的事。
有一个可用的实现,还有几个例子,见extragear。
首个Strigi,Kopete集成将是历史纪录查询。
我们可以利用的历史和联系人列表。然后由Strigi历史将索引引到Akonadi后端。
允许非当前用户使用Kopete而不影响用户设置,象在沙盒中使用一样。
The general consensus of everyone was that Kopete will to move to full Telepathy support in the near future. 但目前Telepathy规范和Decibel并不能满足我们的要求,还不够成熟。这样的移植是必不可少的,大多数人希望在使用Kopete 1.0时保持BC。
准备研究如何把Kopete协议集成到连接管理中。
Why should we split libkopete? Because some code in libkopete is related to
the application itself (and plugins) and others are related to protocol implementation. If we want to be more efficient and have a core library easier to maintain, we should split the library to have two distinct missions, manage the application, and help to implement the protocols.
计划将大部分Telepathy 插件的代码移到核心库中,充分运用Decibel(Telepathy插件不采用)。