23
edits
Difference between revisions of "Google Summer of Code 2022"
Jump to navigation
Jump to search
→QML UI
(→QML UI) |
|||
| Line 216: | Line 216: | ||
''Deliverables / Expected Results:''<br/> | ''Deliverables / Expected Results:''<br/> | ||
* It's a huge task, so expected an implementation of standalone QML/*cross-platform* UI with clear and well-documented API interfaces. | * It's a huge task, so expected an implementation of standalone QML/*cross-platform* UI with clear and well-documented API interfaces. | ||
* The UI may be backed by some mocked C++ code where Psi code should be taken as a guidance. This is perfectly fine to borrow design/API ideas from other clients too. | * The UI may be backed by some mocked C++ code where Psi code should be taken as a guidance. This is perfectly fine to borrow design/API ideas from other clients too. This mocked code is mostly needed to initiate some UI actions unrelated to self user and catch/log UI events. | ||
* 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. | ||