23
edits
(→Dino) |
(→Psi) |
||
Line 202: | Line 202: | ||
* It's assumed the UI will be used not just with Psi. So the branded parts preferably should be kept aside and instead set via API. | * It's assumed the UI will be used not just with Psi. So the branded parts preferably should be kept aside and instead set via API. | ||
* The UI should provide next functions: model/view-based chat/group-chat, roster, avatars, statuses, recent (group-)chats, contact list (with groups/tags), contacts management, own status management. | * The UI should provide next functions: model/view-based chat/group-chat, roster, avatars, statuses, recent (group-)chats, contact list (with groups/tags), contacts management, own status management. | ||
* The UI should be adaptable to screen size (read: there plans to use it mobile platforms too). | |||
* The UI should be compilable at least on Linux, MacOS and Windows. | |||
=== Message Archive Management === | |||
''Brief explanation:'' Support for server-based message archive | |||
''Involved Technologies:'' Qt, C++<br/> | |||
''Relevant readings:'' https://xmpp.org/extensions/xep-0313.html<br/> | |||
''Deliverables / Expected Results:''<br/> | |||
* Implement MAM in iris (https://github.com/psi-im/iris) library. | |||
* Integrate the new message storage with current local history management in Psi (which is based on iris). | |||
* Keep the ability to use local history (for cases when server MAM is unavailable or undesired) and combine both sources seamlessly | |||
* If it's necessary update Psi UI to make it work with the new mechanism. | |||
* Keep in mind related to MAM XEPs to not make something completely incompatible. | |||
= PGPainless = | = PGPainless = |
edits