Aline Gondim Santos authored 2 years ago and Sébastien Blin committed 2 years ago

In conference, this patch depends on using local sinks ids to avoid
mirroring video from sharing resources.

GitLab: jami-client-gnome#1284

Change-Id: I0c74f0780ebf17c68ffcffdca62eb33784189741

GitLab: #990
GitLab: #1016
Change-Id: Ia578493cb60271b284829dbef9179a0fccebbbd2

Change-Id: I981d3db41a2a2fecbece83d1d84f63c48de82888
GitLab: #996

Aline Gondim Santos authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: I76f77f7e5f7eb3e2c46e01f9cdd51b2d40af7739
GitLab: #975

Change-Id: Idc99880fedf8bb9f7a89b5b30c3f316dede89759

Change-Id: Idf38e82631a4e22540aa5dec8ec2db0ab4a38c2e

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: I790f10542aed306a7416a4ce79f2eaf7a770135a
Gitlab: #698

Handle application/edited-message type to support message edition.
Previous bodies are saved in the interaction to be able to get the
original post to avoid unwanted editions.

While loading a conversation, we store the editions in a temporary
map that we link once the edited message is detected. This work
because we can't edit a message before this message exists.
PreviousBodies in interaction.h contains every previous body detected
and the client can show previous version of the message in a popup.

Deleting a message works the same way, just that any message
with an empty body is not shown.

jami-daemon#316

Change-Id: Ib158abd16ad4b629532de11694e88d86a12d72a8

jami-daemon#699

Change-Id: Ia480eef38ee054750ffbaf08ae0aed84090dc9a5

use "voiceActivity" from the conferences informations to show
talking participants

jami-daemon#741

Change-Id: Iaedc61ce485ff03464128b5a17e0a6a0ea9d2c2e

https: //git.jami.net/savoirfairelinux/jami-project/-/issues/1429
Change-Id: Ifec006058e834dacef90539d93c6f1974c84dd52

In preparation for vendoring libjamiclient into 'src/libclient/'.

GitLab: #734
Change-Id: Ibd956abc8fe9bd454ac0e9a5a28b77a5a74174e7

Change-Id: I4176e7ea772c3471f153f8069958566ddcf0c384

+ Finish layout fixing
+ Clean warning
+ protect elements
+ update copyrights

GitLab: #476
Change-Id: Ib3270b5d37d63aa99a576d48574b62801df37258

GitLab: #476
Change-Id: Ic8c7868ae1af8deeb63f8e49f6b05258c9607a99

Change-Id: I7e6093e26546d8207261689069505f1afea2bfbf
GitLab: #476

+ Only load participant's avatar when showed
+ Fix some anchors problems
+ Close popup when adding a new member
+ ParticipantsLayer: make SplitView resizable
+ Better flow

Change-Id: Ied2ac6a64df0ae929effc965d24e08c04b71c288
GitLab: #476

Aline Gondim Santos authored 3 years ago and Sébastien Blin committed 2 years ago

GitLab: #476
Change-Id: I294533b6a1f83e59892ea4c77e0814fb50a70677

Aline Gondim Santos authored 3 years ago and Sébastien Blin committed 2 years ago

fix preview visibility
add yellow margin to active conference participant

GitLab: #435
Change-Id: I865140631b69e9a09f5f88ce314d4d55058cf53c

Change-Id: I8eb66c1c3cddb3bf73b6784a9876dd9dc9c12481

Superposing a MouseArea and a hover in a child
component may cause focus problems.
This replaces MouseArea for a HoverHandler
in the participant moderator menu.

Change-Id: Ic4eb763c79f04198d3a2a2f24636fb2a09dca172
GitLab: #601

Ming Rui Zhang authored 3 years ago and Sébastien Blin committed 3 years ago

Remove unsupported QtQuick One component and it will be
added back in the following patches

Change-Id: Iad206a880096cf956a4220a81dca85a993721fbd

- In another participant video, if I am moderator, I will see local state at bottom and moderator state on top;
- In another participant video, if I am NOT moderator, I will see only one state at bottom representing both local and moderator;
- In my own video, if I am NOT moderator, I will have my local state at bottom left and moderator state top left with a tooltip but no action;
- In my own video, if I am moderator, I will have my local state at bottom left and moderator state top left with an action.

Change-Id: I649d4aeefdd15aa3b554d78948849804ad94a9cd
GitLab: #593

+ microphone
+ share full screen
+ share screen area
+ share file

Change-Id: I5395097ff9f4eead173303594d2916f5b2e1d4d9
GitLab: #592

Aline Gondim Santos authored 3 years ago and Sébastien Blin committed 3 years ago

GitLab: jami-project#855
Change-Id: Ic76b717fb70f5c8aec332f92ed38ecb57fbaaa16

Change-Id: Ia80632cf2e217e8dd6844a6a8c0d0d8c0f6e1baf

Change-Id: Ia344d9f57a216f2d27ef40153af2d6bd787bfb77

Change-Id: I6e912c7a3dbba63f874b063770ba5c68a3f2de2f

gen-resources.py should be used to generate resources.qrc and
JamiResources.qml. Steps to add an image resource:
- add the resource file to the appropriate path under resources/
- run gen-resources.py
- use the newly available resource

Note: only icons and images will be represented by Qml properties.

The resource file generation may be made to run during CMake
configuration in a subsequent commit.

Some unused components were also removed during the refactor.

Gitlab: #477
Change-Id: I8e7f13d465031666be2bbadd5f29f9afc94d210d

Wrap avatars in a Loader to avoid constantly querying the image provider
for remote video participants.

Change-Id: Ieca2457416dfd4c33fc3a960a1e36643ea1f11ef

Throttle avatar image queries to the image provider when the
component size changes.

Gitlab: #466
Change-Id: Ie619671a593bcca75899f3d97c2af2071c427ab4

Gitlab: #466
Change-Id: Id7bd241c3c88dfba90505dd399127d5ceedbf028

Implements a leaner avatar caching system. The avatar component
listens for uid filtering its id, which may be:
- conversation id
- account id
- contact uri

In response to the uid change, a the image source is updated with
a new image url invoking a fresh QQuickImageProvider query. With
this design, only the avatarregistry's uid mapping needs to be
updated when profiles are changed, and no longer should specific
avatar components receive manual source updates.

Gitlab: #466
Change-Id: Ie5313f5c187a0977ca51b890dd92187480a42537

Andreas Traczyk authored 3 years ago and Ming Rui Zhang committed 3 years ago

Change-Id: Idfe409c6e01f8437cba2659e79234a6083bec04e

Gitlab: #441
Change-Id: I1d34c7e766d73026d4c6617592a85ce3a75cc4fa

Change-Id: I42826555d7d490f9361465c1629a45e69f262ab7

Gitlab: #410

Change-Id: Iff3b06b123363478794fd7e419db3d2d0ae10bb7

Unfortunately, QQuickMouseArea force accepts all move events by
design, which makes passthrough events tricky to catch. In-call
overlays for conference participants should be a layer below the
main overlay. So, using QML MouseAreas makes correctly implementing
both overlay fade mechanisms with passthrough for participant menus
too complex. To properly implement the signal relay mechanism we
would need to listen to all the child components with MouseAreas
and relay the positionChanged events to parenting MouseAreas.

To avoid the complexity, we can install an event filter for the
main overlay and listen to global mouse move events that are
contained in it's geometry.

Additionally, we can use Control components instead of transparent
Rectangles to access a hovered property which can be used to
prevent the fade out, and effectively freeze the visibility of menu
components.

Gitlab: #420
Gitlab: #421
Gitlab: #423
Change-Id: I7f05d2bc79ad6a8db0951b7b59e52f671fdf4798

Change-Id: I609452e83edd55a909d0f30aa6cb0daa3687ff3c

GitLab: #379
Change-Id: I885ad338d7a5c06fca7c765680e644c44f33228d