Liam Coursodon authored 1 year ago and Sébastien Blin committed 1 year ago

This commit makes the necessary changes to migrate from Qt 6.5.3 to
Qt 6.6.1 and fixes the following issues:

- EditedPopup.qml: "layout polish loop" and "recursive rearrange"
  errors (GitLab: #1510) as well as an unreported bug where text was
  clipped instead of elided

- BaseContextMenu.qml: QML warning ("Created graphical object was not
  placed in the graphics scene.")

The daemon is also bumped in order to include a patch for a build issue
on openSUSE Leap (GitLab: #1552).

GitLab: #1466
Change-Id: I12df2f84067ebe961368879e08ff7ef275d93395

Broken by https://review.jami.net/c/jami-client-qt/+/26560.
This moves some logic that has been previously duplicated between the app and tests into a common routine.

Change-Id: I40f1af38893cfcef751578d3e4db7d7ba040505b

This simplifies registration and helps with IDE Intellisense for singleton components.

Change-Id: Ifb424491c0fa4777ecc76ec947d57287eea94cfc

The HTML string was being converted to a local 8-bit string prior to parsing with tidy.

According to Qt documentation, this works on Unix systems as toLocal8Bit() is equivalent to toUtf8(), however, it may not on Windows, and may result in character replacement.

Gitlab: #1536
Change-Id: I7aec98cffbd9d72771d1c489f52b38dbb3a1ed9f

- better manage QML interop object lifetimes
- allow intellisense to pick up QML registered symbols
- fix for PreviewEngine threading

Change-Id: I416cdede70b155dc34fc3ee94f428ae2128c8950

When a user misses a call, they receive a message saying so in the chat
and get a notification for that message, but the notification's body was
empty instead of matching the message's content.

Change-Id: I24971d1d0a976ea3ab15ac30c4e9ed33fdf3d760

Change-Id: I52f4e52bbe5fd535b61c459fb7b6dd22ee8f2053

Several major changes to the layout have been made.
- The chat search bar is moved into the message search layout.
- The Searchbar component is stripped of unused features.
- Some remaining logic that was used to switch main loader components is removed.
- ViewCoordinator.getView gets a "force create" parameter and we no longer preload low-cost views.

NOTE: the option to use a frameless window is available within general settings

Gitlab: #1524 (Frameless Window)
Change-Id: Iec6bdf162cb0335d3ae3d9bd09dd9783991a4a57

Seems broken since a recent Qt upgrade. Calling a method in JamiQmlUtils
works as expected.

Change-Id: Ic1257a4f487560744f5ce1ea02928504ff572157

Kateryna Kostiuk authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: I45dca8960401146ca3ac09e6c7ab6e2a2d012655

Andreas Traczyk authored 1 year ago and Sébastien Blin committed 1 year ago

We can't define a property called `status` for a Loader as it exists already. At best, the app will crash as it should be unable to create the chat view. At worst, this will introduce undefined behavior by confounding transfer/loader status assignments and comparisons.

Gitlab: #1537 (crash)
Change-Id: I66fb6da25cae695f7f1f520200f6eed8a2c93d03

Capucine Berthet authored 1 year ago and Capucine Berthet committed 1 year ago

Change-Id: Ic3980ad9ecfa66ec9767aaa1fb18376f196fd012

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

Change-Id: I45a55c57337029d3357bb1059a6d26a9656fe9b1

Change-Id: If94c5e1c24d1a90f7a20f29bafc087d26782fe67
GitLab: #1523

François-Simon Fauteux-Chapleau authored 1 year ago and Sébastien Blin committed 1 year ago

This commit fixes three issues related to tst_MessageOptions.qml:
1) There was no test to check that the call to createSIPAccount() at the
   beginning of test_createMessageOptionsPopup() actually succeeded
2) The created account was not deleted at the end of the test
3) The test would occasionally crash due to an uncaught
   std::out_of_range exception thrown by the
   AccountModelPimpl::slotAccountDetailsChanged function. I've modified
   the function to issue a warning instead, which makes it consistent
   with AccountModelPimpl::slotVolatileAccountDetailsChanged and avoids
   throwing an exception from a Qt slot (which is considered undefined
   behavior according to the Qt documentation)

Change-Id: I4d939b29f27ee27de673aea7046997ef756fbcee

Change-Id: Ib694bfb4bc194e7d6b24bf23f52949715e2efa11

Change-Id: Ifbb9516ce8a10b00b6ef7ec92ee38d71b48cb5a9

- introduce a message handler
- introduce a logging category for the mainapplication object
- demo the filtering

Gitlab: #652
Change-Id: Ice1ea380bb330f576a0936e3048eb4c60a06d4e9

Change-Id: Iddeffd4e2c161ecaf0c9bdb62ed1431d78d0eac5
GitLab: #1493

Else, seems model is not updated correctly

Change-Id: I980a3969b72ebe0d6c702f5fc8c13779603bb8b2
GitLab: #1486

François-Simon Fauteux-Chapleau authored 1 year ago and Sébastien Blin committed 1 year ago

GitLab: #1483
Change-Id: Ib8932ec76519c52547a27e29b095fc60b0e46876

Andreas Traczyk authored 1 year ago and Sébastien Blin committed 1 year ago

WebEngine view destruction crashes on Windows 10 when using Vulkan. Disable the preference for now. It will default to D3D11.

Gitlab: #1515
Change-Id: I8396163a937b3b439569115887020d49e3a8e751

Kateryna Kostiuk authored 1 year ago and Sébastien Blin committed 1 year ago

GitLab: #1513
Change-Id: I7f8e6a8f19ddd932d62a0523e8f95b29851567b2

Kateryna Kostiuk authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: Ib7bac91e802351c699c4a7e44a4c197eeca884e5

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

GitLab: #1509
Change-Id: Ie0d3699f86bd7f7ceffbde1b7d2bff7790919ecf

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

GitLab: #1511

Change-Id: I05c29557683b5d5c88f74ec5916a68bf0d4c17a5

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

GitLab: #1479
Change-Id: I71f84a7089c9ad4dce8b99b340443fd2180df0d4

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

Change-Id: I0c6fb3d7a8f0cf1b30fdec2a505b1ec730ef9f73

GitLab: #1484
Change-Id: I4f8f577c2039ef4a2fc9e4ed731d540e26563b61

Change-Id: I61b3773539bf6a0774ea487e4f5aae74bd2bc635

This avoid a heavy I/O operation on the main pool

Change-Id: Ic5068d9d1c291b8f27ffc563933d4920af42e890
GitLab: #1450

Andreas Traczyk authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: Iff267600c0802fbadedb58174b5fe65bbd1a443f

Change-Id: I3113b860a6a89fc4af1d228840026dc0fd078b9b

Change-Id: I8d5f968fbedbc884c91416246049a0ef4cd652eb

Change-Id: Ifc5d5f4cb5156d75723aac58e1b34ecb5829c2b7

Andreas Traczyk authored 1 year ago and Sébastien Blin committed 1 year ago

Removes some remaining excess complexity in the way interactions are managed by the client. Removes raw iterator access and provides thread-safe alternatives.

Change-Id: I482bf599de869245f96c4aab418127f30508ef41

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

Change-Id: I9c6acd8fe1c34d4ce5b2a172e04eea0f4a1e0148

With Jami-Daemon >= 14.0.0, the client doesn't need to construct
itself the history. This part is now handled by the daemon.
This patch uses the new API:
+ loadConversationMessages->loadConversation
+ SwarmMessageReceived/SwarmMessageUpdated/ReactionAdded/ReactionRemoved
+ remove MessageReceived
+ ConversationLoaded->SwarmLoaded

+ No need to use loadConversationUntil, the daemon will load whatever
the client needs.
+ No need to clear cache, just reset the body and emit data changes

Everything should work like before (even re-translation & changing
preview preference)

Change-Id: Iaf1fa3e84e8e157ae2d0bec210977f9a34415ebc

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

Moreover, add two accounts (for ChatView testing)

Change-Id: Ifb2a45002dd9e86921868257124561764e9b94c5

Xavier Jouslin de Noray authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: Ie1e2495bed08224d6806d0df41124c4b62b7c2e0