ovari authored 2 months ago and Adrien Béraud committed 2 months ago

Change-Id: I553a183700ecdd3b5a8740cb962169a3037e3696

ovari authored 7 months ago and ovari committed 7 months ago

8+3 filename → 8.3 filename
be ware → beware
{cannot, can not, cant, can't, could not, couldn't} → unable to
conpleted → completed
file name → filename
imcomplete → incomplete
informations → information
trying to → attempting to
wrong password → incorrect password

GitLab: jami-client-qt#1730

Change-Id: Ia7757efafd2c06af978db02c65b40b1b77c393f8

Andreas Traczyk authored 1 year ago and Adrien Béraud committed 10 months ago

This approach allows client apps that install ringtones (and any other resources) in custom locations to specify that directory at runtime. This will take precedence over the build time data directory supplied for platforms which install to a fixed path.

https: //git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1619
Change-Id: I81616f79196e645a5ad677d6956be6a2ffcd976a

Sébastien Blin authored 10 months ago and Adrien Béraud committed 10 months ago

"Makefile.am: error: required file './README' not found"

Change-Id: I8729ea1f38bb14893e5cce6ed3f76065e825efb8

The goal of this patch is to allow the clients to get a better
sent/read status from the daemon.

API doesn't change much, but internal logic got some changes. For the
client:
+ SwarmMessage now contains a map<string,int> status where string is the
  uri of a member, int is the status (0 = sending, 1 = sent, 2 = read)
+ cancelMessage is removed as not used anymore (sendMessage with flag=1
  will edit a message)
+ getMessageStatus is removed as the status is sent in the SwarmMessage
+ accountMessageStatusChanged is now emitted for swarm messages when a
  fetch or setDisplay occurs. Client must handle this signal correctly.
+ Previous code to manage last displayed, fetched status is now merged
  with message status
+ Sync info is done when the sync is opened, else status are not updated
  correctly

GitLab: #948
Change-Id: I60763d4de8a995c6fc9f6df6434e266211f8dc2f

Jami crashes on openSUSE Leap 15.5 due to a segmentation fault in gnutls
3.7.3.

Change-Id: Iba3705b48c7f5817eb644bab1cbf84d4536d6d04

Alexander Lussier-Cullen authored 1 year ago and Sébastien Blin committed 1 year ago

GitLab: #831

Change-Id: I8e2aa205629735df043618a87e54ae6a43e6ca3f

Change-Id: Ic8b28a32f64862ac2dfae074d06f4eac470ab7e1

This heavily changes the API for the client. The goal here is
to move the logic to construct the history to show in the daemon
and not the client. This has several advantages:

1. Logic is common across every platforms, so bugs should not be
platform-specific
2. Client got less logic
3. Signal are simplified, if an edition comes, "MessageUpdated"
will be triggered instead MessageReceived.
4. Some tests are added for linearizing the history.
5. Search on edition is fixed.

Tests got heavily re-written, but the content didn't change (2 tests
are added, the rest is simplification).

GitLab: #831
Change-Id: Ie7c81077067e9e49db1dd396829c9225c0512c16

Change-Id: I339a0689d460c7561cc60325819d795cb32261d4

Aline Gondim Santos authored 1 year ago and Sébastien Blin committed 1 year ago

GitLab: #485
Change-Id: I0ae7c23da2a1f2384699639cc0de58f8f05b33ec

Aline Gondim Santos authored 1 year ago and Sébastien Blin committed 1 year ago

GitLab: #485
Change-Id: Ie3f129cd0cee14a97764eb22ee2b5f530a3f3023

Andreas Traczyk authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I0e142f271fa0db3c3d4af1e57919ef1f65beb8c2

Maxim Cournoyer authored 1 year ago and Sébastien Blin committed 1 year ago

This is a follow-up commit to
3dd5f4eb ("dbus: use sdbus-c++ for
dbus communications").  The build should abort if the sdbus-c++ module
is missing (it's "required" on the CMake side, so why shouldn't it be
on the Autotools one?).

* configure.ac: Fail when sdbus-c++ is not found.  Quote the
sdbus-c++-xml2cpp command.

Change-Id: I8268abec10ba5be0eb8b520988affc9c0345a4fb

Change-Id: Ia6d43b818b705c13da979d90920ff2df585f5cec

GitLab: #851
Change-Id: I3bbb529eccb3dbb6389621dbfc38f5cf081a98ad

Adrien Béraud authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: Ib53b7e170df59f873fbd85f6e7d4bf338d04cb9c

Vladimir Stoiakin authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: If10740b4fd192a1043c5f83adc9072fe67df7862

Change-Id: I94da5dedff8f29e38f7aa517cf2212f5142d8f29

Adrien Béraud authored 2 years ago and Sébastien Blin committed 2 years ago

If we add the define, we must also build the file.

Change-Id: Id336770ed7f7df02e26074b01aed25bad75f9288

Sébastien Blin authored 2 years ago and Adrien Béraud committed 2 years ago

Change-Id: I35d51deb450a265fd7541bad2735b8dd4ca465c5

Change-Id: I77ac99c455f4f903bb9c48b02eacdbedc5faf066

Change-Id: Idfd2a086847f9665c57e83a8184c20957fec9664

Change-Id: Ia80fc12ba65b1abd516af205e6664261ae2e33fe

This patch introduces the ability to start calls and extends the
usage of rendezvous points to swarm with multiple participants.

When starting a call in a swarm with multiple participats, one device
will work as the host of the conference, and the caller will
immediately start the call alone.
Other peers will receive a commit and a notification to be able
to join the active call. To join a call, users needs to call
rdv:uri/device/convId/confId to be added (if authorized) to the conf.

There are some majors differences in the process.
First, every conversation will be able to decide a default host
for conferences. This still needs some design and will be
introduced in another patch. For now, the caller is the host.
Then, because all members of the call may not be interested to join
a call, or they may want to get several calls at the same time, the
system must be able to manage more than one active calls (e.g. a
company with multiple projects can do several standups at the same
time).
Finally, in the conversation, two commits will be generated to be
able to know what active calls are available. The first is
announcing that a conference started, the second announces that
the conference stopped (the host closed the call).
However, this introduces a difficulty. The host may crash and not
commit the end of the call in time. In this case, hostedCalls are
stored in a file and the conversation is updated during the init
of the daemon.

Change-Id: I081a4920edb3773bbed884ae50f34e476ad42094
Documentation: https://docs.jami.net/technical/swarm.html#call-in-swarm
GitLab: #312

Olivier Dion authored 2 years ago and Sébastien Blin committed 2 years ago

It's not possible to replace the DRing namespace for jami because of conflicts
with namespaces and classes defined under the jami namespace.  Thus, use libjami
as the namespace.

Script to reproduce:

 rg -l DRing | sort | uniq | awk '$0 !~ /NEWS/' | xargs sed -i -e 's|DRing|libjami|g'
 rg -l DRING_ | sort | uniq | xargs sed -i -e 's|DRING_|LIBJAMI_|g'
 sed -i -e 's|dring|jami|g' src/jami/CMakeLists.txt
 sed -i -e 's|dring|jami|g' src/jami/def.h

Change-Id: I80e8c8b58a7586527a016bbef850bab07869c473

For now, only be able to edit messages from our-self and with the
text/plain type

Change-Id: I20c6ed7dad3892f0fa655812242b9ca6e77e69b3
GitLab: #316

Sébastien Blin authored 2 years ago and Adrien Béraud committed 2 years ago

FMT_COMPILE is needed

Change-Id: Ic7f7948d2816dc0017f9b780046e4ce9f31b4c9c

This store user's preferences per conversation into
conversation_data/<convId>/preferences
In this way, the daemon is able to sync this file across devices
and remove preferences at the same time we remove the conversation.

For now, only support "color" and "ignoreNotifications"

The preferences are synced via partial SyncMsg sent across devices.

Change-Id: I8fe74cc06733ad61d45d721e0264b1941d4cf122

Change-Id: If13a246aa50953c99d72937daeb7866de2d82e8d

Change-Id: Id123f733759d6147f0f8fb9975b21fd8b0f1e558

Causes issues with yaml-cpp. Reverting temporarily until we fix the issue.

Change-Id: I2df0823554ad87880bc965bdff4f4707a6129789

Vladimir Stoiakin authored 2 years ago and Andreas Traczyk committed 2 years ago

Change-Id: Iceae2a19ce3febce62f7916af8b4242e06a7e1d4

Change-Id: I238f452f77e10c16ebc5f69bef1b768f44e57e2e

Olivier Dion authored 2 years ago and Sébastien Blin committed 2 years ago

These tests were never run on the CI and are not even in the build of Meson.

Change-Id: I0109633de2fd03b8589734d92c039b34d5b729bc

Change-Id: I561e60a14a363bb8a1658eb7f740bd67a85c2d99

+ Bump deamon version to enable multistream
+ use signal for recorder to check if file stopped
+ answerMediaChangeRequest pass isRemote for tests

Change-Id: I396b8246264cb7826350f75e74f20f05b864f384

Change-Id: Idffdb3f6669398db165cbec9607af7ed2c56fb21

Change-Id: Id6967f8fd0976caae81e4c951d0d5dc9901b23d3

Change-Id: I386bd1adddf403ff450e5d22688337b7d6d7c1f6