This will allow the addition of custom parameters to a second anchored window.

"Conversation ID" and "Force local preview" are implemented.

Change-Id: I2366b57e6bb36efb568b06e40ef124a440a39397

Change-Id: I8d5f968fbedbc884c91416246049a0ef4cd652eb

Capucine Berthet authored 1 year ago and Sébastien Blin committed 1 year ago

It works with a Pimpl which the right pttlistener.cpp depending
on the platform you are on (macOs, windows or X11). It is a
global PTT which listen to key events during calls. If the
global PTT is not supported, a local PTT is set.

jami-project#1402

Change-Id: I8399800966c737bb8e8a656ecbb6af7ac7cdde8c

GitLab: #1073

Change-Id: I7dc2ab632170a959b8d29979deacd3fb03ff6671

Introduces the ViewCoordinator component to promote dynamic view loading and reduce coupling between components.

The following objects are now created and destroyed as needed:
- SettingsView
- WizardView
- dialogs

Further refactoring will be required in order to do the same with the ConversationView, which now parents the ChatView and the CallStackView.

Gitlab: #897
Change-Id: Ice6a0c133e62e1e0c8d7fb99ec2c41234c049b59

Change-Id: Idf38e82631a4e22540aa5dec8ec2db0ab4a38c2e

Change-Id: I5030cb4a5b53f4828485792f82e7241ecd06164c
GitLab: #810

Sébastien Blin authored 2 years ago and Amin Bandali committed 2 years ago

Change-Id: Idc960c96e4647dbb6f8c1d64f545fe25c80bbaa5

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

GitLab: #734
Change-Id: Ibd956abc8fe9bd454ac0e9a5a28b77a5a74174e7

Change-Id: I8eb66c1c3cddb3bf73b6784a9876dd9dc9c12481

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

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

Change-Id: I9d073cb5203a887fd5e39ced258b19e0196d069b

Gitlab: #411
Change-Id: Id987ad1b3c0c583425a53b85735ab7eb3f434036

Gitlab: #410

Change-Id: Iff3b06b123363478794fd7e419db3d2d0ae10bb7

- minor cosmetic changes to the call view overlay
- add the ability to change audio/video input during a call
  from the call screen overlay

Gitlab: #411
Change-Id: Id6bbb2278d807f3bd7ad1478db405669088584ce

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

Introduce a model to manage the overlay logic.

It is not used in this commit.

Gitlab: #411
Change-Id: I6a666fe00e7f66c7e217ae1f77360327e83fdcd6