Skip to content

Conversation

r10s
Copy link
Contributor

@r10s r10s commented Sep 4, 2025

a dedicated viewtype allows the UI to show a more advanced UI, but even when using the defaults,
it has the advantage that incoming/outgoing and the date are directly visible.

successor of #6650

@r10s r10s force-pushed the r10s/call-type branch 5 times, most recently from 0fceeba to 8d4bf03 Compare September 4, 2025 13:28
a dedicated viewtype allows the UI to show a more advanced UI,
but even when using the defaults,
it has the advantage that incoming/outgoing and the date are directly visible.
@r10s r10s requested review from adbenitez and link2xt September 4, 2025 13:58
@r10s r10s marked this pull request as ready for review September 4, 2025 13:58
@r10s
Copy link
Contributor Author

r10s commented Sep 4, 2025

merging that in, we're actively testing, and it does not affect other core parts

@r10s r10s merged commit bed1623 into main Sep 4, 2025
29 checks passed
@r10s r10s deleted the r10s/call-type branch September 4, 2025 14:51
r10s added a commit that referenced this pull request Sep 5, 2025
this PR uses the initial "call messages" (that has a separate viewtype
since #7174) to show all call status.

this is what most other messengers are doing as well. additional "info
messages" after a call are no longer needed.

on the wire, as we cannot pickpack on visible info messages, we use
hidden messages, similar to eg. webxdc status updates.

in future PR, it is planned to allow getting call state as a json, so
that UI can render nicely. it is then decided if we want to translate
the strings in the core.

<img width="320" alt="IMG_0150"
src="https://github.com/user-attachments/assets/41ee3fa3-8be4-42c3-8dd9-d20f49881650"
/>

successor of #6650
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants