Change-Id: Idc99880fedf8bb9f7a89b5b30c3f316dede89759

Change-Id: Idf38e82631a4e22540aa5dec8ec2db0ab4a38c2e

Change-Id: I873b0a46b16b7e269882fa7b70966063047884bc

Change-Id: I46e3ef0d00b3db97f4908d84e7b251ee67a861c7

Change-Id: I7d59a8f1cfd01469463864905c3f2ad983afeb95
GitLab: #961

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

Iterate through CPP elements and use positionView(ListView.Center)
as other approach seems bugguy or slower.

Change-Id: I43879969ccb457166879a156efb482e77ff07d6b

Else, changing the moderator state of a participant doesn't
refresh the controls

Change-Id: Ic00a7836b181bf9aa9c9d793720323bc2247196a

Change-Id: I3f26a4f38ae3e68e36c8121b33108363bbb06291

We sort the invites by last interactions. However on swarm, there
is no interaction yet. Add one with the received timestamp given
by the daemon.
(Regression appears because we were showing trust request before
not conversation requests)

Change-Id: Ic7f4d1a5d485325c95a19c2c38ae9c74630829ce
GitLab: #956

Calling a conference and stopping the call will lead the camera
opened. This code seems useless and bugguy.

Change-Id: Iff06b03838a2e13fe378f60f84df96ceb7735f1f

If the avatar for an account is set on a device, it will send
to detected devices on new connections. The client was ignoring
the new avatar if it was not empty, now we just use the last
received avatar

Change-Id: I0b2cde9c193d46014c4d600775743312219b84df

Change-Id: I6e04c8e01e87f66a9e6da4fb32524f085066a5d0
GitLab: #940

Some types where missing, causing the chatview to not show all
messages.

Change-Id: I2ac1dfa03de8330b38f2828e66eead7114b2cfe6

If the timestamp is shown on a contact message, the line was not
taking the full width like other messages.

Change-Id: I94a448acb4f7fd6400365445dd912abc5103ea2a

Fadi Shehadeh authored 2 years ago and Sébastien Blin committed 2 years ago

- isEmojiOnly changed to message containing only an emoji, not an edit or reply.
- adapted size

GitLab: #957

Change-Id: I78388a406a2a0b9c93f1c291850062fd9bf04a54

GitLab: #954

Change-Id: I6fe7537b0de7fb904a05159072476003ee835eea

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

- Standard time/date is now used
- If today, show local time, otherwise show local date

GitLab: #545
Change-Id: I07f1e706868c725d1c917c473dc0fdbad8d6810f

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

- Contributor added to credits

Change-Id: I27d459557c10e50c53b342472ed76c2c7966ff37

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

* extras/packaging/gnu-linux/scripts/release-version.sh: Add script
for deriving (reproducibly) a release version.  The format will follow
a 'YYYYMMDD.X' scheme, where 'YYYYMMDD' is the date of the last commit
on the current branch, and 'X' the number of releases tagged that day,
starting from zero.  Example: the first stable release with a newest
commit date of 2023-01-02 would have a version of '20230102.0', the
subsequent one '20230102.1', and so on.  This is derived by counting
the number of git tags with the prefix 'TYPE/YYYYMMDD', where 'TYPE'
is the release type: either 'stable', 'beta', or 'nightly'.
* extras/packaging/gnu-linux/Jenkinsfile: Call the above new script to
derive the release version to use for tagging.
* extras/packaging/gnu-linux/Makefile: Switch from the previous
'jami_YYYYMMDD.hhmm.COMMIT.tar.gz' tarball filename format to
'jami-YYYYMMDD.X.tar.gz'.  The new format is shorter, omits the
unnecessary and confusing commit id, and uses dash instead of
underscore.  Also, it contains everything in a top-level directory
with the same name as the tarball (without the .tar.gz extensions),
so that 'jami-YYYYMMDD.X.tar.gz' nicely extracts to 'jami-YYYYMMDD.X'.
With these changes, our release tarballs will follow more closely the
related instructions from the GNU maintainers manual:
https://www.gnu.org/prep/maintain/html_node/Distribution-tar-Files.html
Lastly, this change inadvertently 'fixes' a recent issue where the
'extras/ci/client-qt-gnulinux' subdirectory and its contents would be
moved to top-level in the tarball due to one of the tarball transforms
matching the 'client-qt' in the directory's name, replacing the
'extras/ci/client-qt' prefix with 'client-qt', thereby resulting in
'client-qt-gnulinux' being moved to the tarball's top-level.
* .gitignore: Ignore several packaging-related directories and files.
* extras/packaging/gnu-linux/rules/rpm/jami-daemon.spec:
* extras/packaging/gnu-linux/rules/rpm/jami-libclient.spec:
* extras/packaging/gnu-linux/rules/rpm/jami-qt.spec:
* extras/packaging/gnu-linux/rules/rpm/jami.spec: Update the expected
release tarball filename pattern in the 'Source' field.  Also replace
references to previous top-level directory name 'client-qt' with the
new one 'jami-%{version}' where needed.
* extras/packaging/gnu-linux/rules/rpm/jami-libqt.spec: Update the
'Source' field to follow new tarball name consistent with the main
Jami release tarball.
* extras/packaging/gnu-linux/scripts/build-package-rpm.sh: Update the
tarball top-level directory pattern for the new format, now passing
the --wildcards option to GNU Tar.  Also use a name for the jami-libqt
source tarball that is more consistent with the main Jami release
tarball.
* extras/packaging/gnu-linux/scripts/build-package-snap.sh: Update the
top-level directory pattern for the new format.
* extras/packaging/gnu-linux/tarballs.manifest: Drop file accidentally
checked into git.

Change-Id: I2695f560c0bc5e61fb99dc0244f8fbb8e7026a62

Change-Id: Ib11d464284effa5e78ca56441d0e535858071151
GitLab: #941

Because in a swarm you can talk with non contacts, we should at
least retrieve the username when possible.

Change-Id: Ie01cd10cc1231fc4024bd5a08c30c08d69e8e7f0
GitLab: #948

Change-Id: I9eb8843d50fdeb914eae622c15555b366d246094

Nicolas Vengeon authored 2 years ago and Andreas Traczyk committed 2 years ago

SFPM performs poorly compared to its C++ counterpart in cases where re-filtering often is required. Tests show SFPM taking roughly 10x that of QSFPM in certain cases when the entire conversation needs to be loaded.

Change-Id: I25792f0ab376ae11d42073a548934b743e59fa3e

Change-Id: I6c36ab045667d01859a72dfec12e3e02130c57fe
GitLab: #947

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

Change-Id: I6ef8069de9012e235fe6f8907b9d2bb94a44cd40
GitLab: #634

Change-Id: I3501d0ba072bc68685af8ba8c46c22979cc25493

Change-Id: I3fcb60aed90e3a7cf7edee7f8ac28c204dbb8952

So that users can know when a message is deleted and can check
previous version like any edited version.

Change-Id: If3c1daeec930bd4b0f359573b971790199397489

Aline Gondim Santos authored 2 years ago and Andreas Traczyk committed 2 years ago

Change-Id: Ie1708ae4be049206fb8337db1211b7844e45726f

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

Change-Id: I790f10542aed306a7416a4ce79f2eaf7a770135a
Gitlab: #698

This patch sets up app updates to use EdDSA signature as now
it is required by Sparkle

Change-Id: I68a581e21850f04a819f4fe7ea49a33766031e01

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

Change-Id: Ica33126a1d75b4880c70c1e7f654f82db6499bbd

Scenario, create a swarm with self.
As a warning, it will show "Can't find contact YOUR_ID  this is a
bug, please report" because your account is not in your contacts.

Change-Id: I6f49f8fa77132daf00396b62da9ded470df49f98

Else, the text was overflowing

Change-Id: Idd27682d612cc35fce045967025df49ad1a1a202

If a user join a conference with video enabled, but without any
valid camera and try to un-mute/mute in loop, it will add
new empty medias with incorrect sources causing duplicated participants
in the conference.

Change-Id: Ifa0dc090ca49ae6f9799f1209f3514cf540365da

This reverts commit ab8c3645.

Reason for revert: It breaks the sharing functionality in windows

Change-Id: Ia031bec6d82462115e3086ab9300b3aef99d9bab

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

GitLab: #634
Change-Id: I4c95622297e52d4b7fb5ea42426353a3b3579186

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

Change-Id: If3ee1fd3f074e8807fedc66fc02758df62789b39

1. sourceParent and destinationParent were incorrect.
2. Moving always all the message can be incorrect if parentIdx >
msgIdx after a merge

Change-Id: I0ab8eeabb61926d5c0c22d8fed68c60d54178bf6
GitLab: #939

Change-Id: I7bd12dbc3bf512b3cd880892d2afda17c8117bd6
GitLab: #862