Change-Id: I75e617eb84d96d2afa0b43d6c50b5d7832ec4012

Change-Id: I5d3d7cd5cb7570ff2063ea5a981c312480a6990a

+ Add call buttons to start a new call
+ React to events from the swarm
+ call interactions (Join call/Call ended, etc)
+ active calls area
+ Add call management logic in LRC
+ Feature is enabled via the experimental checkbox

jami-daemon#312
Change-Id: I83fd20b5e772097c0792bdc66feec69b0cb0009a

Save current color, and notification's preferences

Change-Id: I3197be53bf622528aa3bc2e3f0d9aea29068e144

Sébastien Blin authored 2 years ago and Andreas Traczyk committed 2 years ago

Change-Id: Ia6d7ba0ee9e32d5830b35b863b3981e2487df183
GitLab: #821

Asking jami to launch another instance with ./jami-qt jami:xxx
will search for "xxx" inside the application and select the
conversation if found.
This allow to support webpage with <a href="jami:username">

For GNU/Linux, in the .desktop file, x-scheme-handler/jami is
added.
For packaging, we will need to determine if the scheme is handled
automatically. For now, to test, we need to add:

x-scheme-handler/jami=jami-qt.desktop;

in "~/.config/mimeapps.list" (and jami-qt.desktop) should
be in a valid path.

Change-Id: Ibbb6e8942f1873d81a57640bdf6f839885981be3
GitLab: #655

A signal exists for showing errors to the user to make failing cases
more explicit. With this patch, errors detected are displayed to
the end user so that they know that an error occured and what
kind of error occured.

Change-Id: Ib2d4d4fdb171235e0598de0f1c190b8fd0fcc336

+ Remove readOnly from conversation's as it was never used
and not necessary in multi swarm as you can re-add members anyway
so it's never read only.
+ Makes non swarm conversations just readable.
Users can save whatever they want and replace old non migrated
conversations to new swarm.

Change-Id: I8aa2521bc524b6159d7ba0b613834438e293e09e

For multiple swarms, the description will be shown from the profile,
for core dialogs, the best Id is used.

Change-Id: Ieb7d5f143c1a85c4c629a5a8a03850fa1ebddf63

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

GitLab: #734
Change-Id: Ibd956abc8fe9bd454ac0e9a5a28b77a5a74174e7

GitLab: #670
Change-Id: Ie8eb123c0fc7506863b06c7b588ef7806b9a077a

This is the first version of the members list for swarm creation.
The user is able to select 1:1 conversation, search new users and
merge swarm members in a new swarm.

Change-Id: Ic9ac1e9324a46f70ad5d285df890a01ca459f3fa
GitLab: #670

In the members list, a right click allow the user to access some
actions such as:

+ Perform a video or audio call with a member
+ Open a 1:1 conversation with this member
+ Block this contact
+ If allowed, kick a member from the conversation

In the future, other actions can be added, such as promote a user
to administrator.

GitLab: #340
Change-Id: I3824ad4efa8faf89479e99c93b98d3dd9781582d

GitLab: #340
Change-Id: Ib5d3d44c620120b050fca57c774edfe2b3de7c93

GitLab: #340
Change-Id: I4a4ebfbebb880161e93fc0a086eec13ffb1ba285

GitLab: #340
Change-Id: I72534e9e3599b70cdf0f91aa81be7636499715b8

This reverts commit 0c1b1cd4.

Reason for revert: #658 (comment 33744)

Change-Id: I5bdacea0bd414fe270697566d08db20f279e9349

It's more useful than the welcome view

GitLab: #645
Change-Id: Icf79aaff5c2cd1d9faf8481ba20f68e7b095d8c1

Change-Id: I8eb66c1c3cddb3bf73b6784a9876dd9dc9c12481

Adds a new chat view footer to describe for read-only conversations
to describe the concept and provide options to remove the contact
or restart a new conversation with the contact.

Gitlab: #475
Change-Id: I6ca0e8dfbf49f17a6ff93a2744c552b76d923773

depends on: https://review.jami.net/c/ring-lrc/+/18979

Change-Id: Ic29e5a6f6eced04a095dd097352c37ca0b253eda

Read-only conversation has:
- a lock icon in the smartlist item
- no message send bar in the chat view
- no call actions available from the chat view header
- no call actions available from the smartlist context menu
- no double click to call

Change-Id: I0497b94038b450f0a0a22fc007de1281b7b2214d
Gitlab: #475

Change-Id: I85a070e8ea44b108fa75d69a8c6f544e8e2c8581

Filter either the same conv id or peer list of the currently
selected item when responding to the conversationReady signal.

For dialogs we make sure the peer list(1) is same and for all other
swarm conversations we match the conv id.

This will prevent programmatic auto-selection of the smartlist
during account sync.

Depends on: https://review.jami.net/c/ring-lrc/+/18793

Change-Id: I6cedb8494f7c001bf886fe36dd03adffd201bb51

Gitlab: #471

Change-Id: I00db0c43c76f46ab934a196df1896005d936f4ff

Sébastien Blin authored 3 years ago and Andreas Traczyk committed 3 years ago

Also use jami.svg for regular systray icon.

Change-Id: I6325c756d10216a017eb89042ab2f6ca0e988703

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

Using a custom getter setter cause the setting of the value to
require manual changed signal emission and in addition to being
error prone, this prevents the changed signal from being emitted
upon initial selection. Some excess workaround code may be removed
in following commits.

This patch also refactors the banned contact signaling as part of
an accountadapter connection cleanup.

Change-Id: I73fb751001e53e086adc7a6a8d706671c2878a77

This fix notification's actions for the notification, finding the
correct convId.

GitLab: #455
Change-Id: I9b70f723eacd930f95c2eaf01ecd52b8c5d28313

Removes profile type filter entirely. Treats swarm and non-swarm
differently when accessing role data.

depends on https://review.jami.net/c/ring-lrc/+/18656 for changes to
helper function names in conversation::Info

Change-Id: Ife69d4c70072ea524fed873136fd9ec39632d6d8

Sébastien Blin authored 3 years ago and Andreas Traczyk committed 3 years ago

Change-Id: Ifa7ae09d5edc274a200fcf9d934ac27fe7c71956
GitLab: #455

Sébastien Blin authored 3 years ago and Andreas Traczyk committed 3 years ago

Change-Id: I18e50cc29ce4183a1d3c89f1e30f9ddb61248278

Sébastien Blin authored 3 years ago and Andreas Traczyk committed 3 years ago

Change-Id: Ib3e01a0af51736727b8056ed9eaa8ce9170c2d6c
GitLab: #438

conversationModel is a unique_ptr

Change-Id: If3f85387c3f322c83abe5921705ab6e8addf8373

Andreas Traczyk authored 3 years ago and Sébastien Blin committed 3 years ago

When the needsSyncingSet signal is caught, we need to update the
UI to change filter tab, reload the conversation, etc.

Change-Id: I70170d75afa50acad6e79d53fcaeb82752c38e81

Andreas Traczyk authored 3 years ago and Sébastien Blin committed 3 years ago

To accept incoming requests, a new acceptConversationRequest api
should be used and makePermanent is now only called for outgoing
requests.

Change-Id: I70bcfc0e323ae250641420f4fda91c6987cac720

Change-Id: Icbf4b20ae23360262d6ed0214101c8775ac9e9d8

This should fix a race condition preventing the right conversation
from being selected after an outgoing interaction and, more rarely,
accepting an invitation.

Change-Id: Iccd1f91ba4d46285c2f1e4594122a736824b752f

Set the account and request filters separately.

Change-Id: Ib7d93caa4058e086d3cbcf39ac3fb9a30097aba1

PENDING profile is no longer a valid filter criteria. isReqeust is
now used instead and the profile type is restricted to account
types and tracked as a separate property.

Change-Id: I4848e32f005ea7a6a8b5f2fa25d40b7e1e4d63b8