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

Change-Id: I8d5f968fbedbc884c91416246049a0ef4cd652eb

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

This reverts commit 87aed4c0.

Reason for revert: Breaks Wayland support (without Xwayland)

Change-Id: I27a26cf784b3eea543b9cc396a130e80f295b81b

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

This commit addresses an issue where the GTK theme was not being correctly applied when running our application on Wayland with the Wayland platform plugin. Although the root cause is not entirely clear, it seems related to a known Qt bug (QTBUG-99684). As a workaround, we're setting the `QT_QPA_PLATFORM` environment variable to use XCB with Wayland as a fallback. This ensures that the GTK theme is applied correctly when X11 is available, while still allowing a fallback to Wayland in its absence.

Possibly related issue: https://bugreports.qt.io/browse/QTBUG-99684

Gitlab: #1156
Change-Id: I71ef4e39f916d9871134fb0caded8b30bff578fb

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

Remove trailing webengine parameters by not synthesizing command-line args. Use the env var QTWEBENGINE_CHROMIUM_FLAGS instead.

Gitlab: #1074
Change-Id: Ibc2a4f75317bd502a3cca96758ef72264babe255

Now we can validate vulkan without creating an instance.

Gitlab: #938
Change-Id: I9543986b33974083c1aec42128dfe1b924134116

Change-Id: I1210f5ca8c98d80aea0bcc6f8591aba4a968b07b

Change-Id: Idf38e82631a4e22540aa5dec8ec2db0ab4a38c2e

Maxim Cournoyer authored 2 years ago and Amin Bandali committed 2 years ago

Now that there is no longer a second official client (jami-gnome), we
can remove this uninteresting implementation detail from the name.

Mostly automated via:

  $ git grep jami-qt -l | xargs sed 's/jami-qt/jami/g' -i

* src/app/jami: Delete launcher script.
* CMakeLists.txt: Un-register it from installation.

Change-Id: I5167c29089feb4e64c12d7d01c1ce281e16c0613

Vladimir Stoiakin authored 2 years ago and Sébastien Blin committed 2 years ago

GitLab: #743
Change-Id: I324d2e7923b4d3c907f4edf89b2db7f9f998a50c

Add another supplementary check using functions from the vulkan-1
module before trying with QVulkanInstance.

Gitlab: #746
Change-Id: I8975ef8765675aca95c4fee648853ea74c0c8ec9

Add a supplementary check after calling QVulkanInstance::create to
make sure the requested validation layer was created.

Gitlab: #746
Change-Id: Ibe3004fa1a1a38401be8625aaea34e0bef185d0a

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

GitLab: #734
Change-Id: Ibd956abc8fe9bd454ac0e9a5a28b77a5a74174e7

Kateryna Kostiuk authored 2 years ago and Amin Bandali committed 2 years ago

This patch allows building the project without Qt WebEngine, by
disabling (for the time being) the features that depend on it:
the emoji picker, link previews, and media file previews in the
chatview.

Co-authored-by: Andreas Traczyk <andreas.traczyk@savoirfairelinux.com>
Co-authored-by: Amin Bandali <amin.bandali@savoirfairelinux.com>
Change-Id: I74751b0cc6f22c61a6fd7281ca3207e0fdbb2212

Some drivers seems to create weird results.

Change-Id: I9bea2c7f8fca8cd9ae6681981b2e30b2848ffeaf
GitLab: #718

Fallback to openGL if metal is not supported.

GitLab: jami-project#1413

Change-Id: Id8ac4c817d0b65243becc9963a8bba6621feaf82

Andreas Traczyk authored 3 years ago and Amin Bandali committed 3 years ago

+ Use Vulkan if we can create a Vulkan instance.
+ Log the window's effective graphics backend.

GitLab: #630
Change-Id: I1e114a3a7388b84766361afda351d1ea4a4c0322

Change-Id: I69f60964de48c770d5467c3231430a49b31e411e
GitLab: #603

We've had reports of missing vulkan dependencies on fresh Windows
10 installs. Until this has been investigated, we should keep the
default rendering backend at the cost of some flicker.

Change-Id: Idaab06ff80d7841231270a207cceb134f8d790b0

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

GitLab: #603
Change-Id: I271f6d4b9b8089dc88479f1d7d98514acb3d52be

+ Refactors some window management logic in LayoutManagar.qml.
+ Refactors app start to support both a minimized start and a start
  URI. The start URI should force visibility.
+ StartMinimized now starts the application in a closed-to-tray
  state, instead of a minimized state.
+ The close-to-tray feature now saves the previous windowed state.
+ InstanceManager handles URI transfer to secondary instances.

This commit does not implement URI handling. The original
implementation supported only calls via a user infohash as the URI
parameter. A new and flexible protocol should be defined to support
multiple Jami features.

Gitlab: #655
Change-Id: I2c47028930e4e9d7ccca94d9362545df14b98160

To coordinate the MSI installer with Jami's close-to-tray feature,
a custom action was used to kill QtWebEngineProcess and Jami, prior
to the file installation step. The close-to-tray feature makes it
so the only way to terminate the app is via the systray context
menu.

This patch harnesses the IPC mechanism used by the run-guard, and
adds a command-line option('--term') used to signal the secondary
process and provoke graceful termination.

The benefits are:
- the app can save data before closing
- system tray icons aren't left dangling after updates
- QtWebEngineProcess is guaranteed to be terminated during install

Gitlab: #654
Gitlab: #543
Change-Id: I79421eeab49c9ec0826010af99a364471bb81d1a

In 64720224, a no-sandbox flag was
added because QtWebEngine can't load fonts on recent glibc. Source:
https://bugreports.qt.io/browse/QTBUG-92969
https://bugs.chromium.org/p/chromium/issues/detail?id=1164975

Now, we use Qt 6.2, so this flag should not be necessary.
So, we can finally close #442 without any dirty workaround.

GitLab: #442
Change-Id: I52835e40d37d2397a891415fd2b1dd8dd4048b8b

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

* src/main.cpp (main): unset QT_STYLE_OVERRIDE.  Some distros, like
Zorin OS, set QT_STYLE_OVERRIDE to force a particular Qt style.
This has been fine with Qt5 even when using our own Qt package
which may not have that style/theme available.  However, with Qt6,
attempting to override to a nonexistent style seems to result in the
main window simply not showing.  So here we unset this variable, also
because jami-qt currently has the Material style hard-coded anyway.
https://bugreports.qt.io/browse/QTBUG-99889

Change-Id: Ic261b46baf79cf36491578ff969b398b95363c94

Change-Id: I8eb66c1c3cddb3bf73b6784a9876dd9dc9c12481

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

Qt on Windows defaults to Direct3D rendering backend which causes
flickering and visualy glitchy resizing.

Gitlab: #601
Change-Id: I175d6131aca234f557234a23984e46f94c7d5417

Change-Id: Ib92cf40dafd02f1bdc55ba51bfce0744fe4d88fc

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

Change-Id: I0e02cd89039ff8573c1b8ab974d19976151b4c38

Seems bugguy on some distributions...

Change-Id: I985d64cc36445ce2b68fe091ad060601071a3e04

1. Add --single-process
2. Rename the httpUserAgent to jami-qt

Change-Id: I6de29ee89176b453f12ce225acf926dd1b819c18

QtWebEngine can't load fonts on recent glibc. Source:
https://bugreports.qt.io/browse/QTBUG-92969
https://bugs.chromium.org/p/chromium/issues/detail?id=1164975

I don't want to have custom patched Qt version running for Jami,
so, for now disable sandboxing to fix font loading and wait for a
fixed Qt version.

GitLab: #442
Change-Id: Ia0918b6c47dc8a9bcfed8556043b5163e4963248

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

Change-Id: I97f256873bbffd79eb08707f0a809172bca06e6b

GitLab: #337

Change-Id: Ifb671d38d364714818650a8154c43a5787460039

Ming Rui Zhang authored 4 years ago and Andreas Traczyk committed 4 years ago

Gitlab: #302
Change-Id: I3d79443b4338a27a8724600be233a2ff765427f9

Ming Rui Zhang authored 4 years ago and Ming Rui Zhang committed 4 years ago

Gitlab: #160
Change-Id: Ica0aab9ba7f043c4ab56314bbd5312f75239ad51

Albert Babí Oller authored 4 years ago and Andreas Traczyk committed 4 years ago

- add QtQuickTest, QtTest and googletest support
- create tests folder within cmake hierarchy
- avoid using wildcards in Dockerfile

Change-Id: I81661a86757f01333538908dbc81a0bafae00ab7

Andreas Traczyk authored 4 years ago and Ming Rui Zhang committed 4 years ago

Change-Id: I6931f3239c4b9ca19d54272587ae8c97cf02b16b

- also re-enables the disable-web-security flag

Change-Id: Iabbae6bd78e30be91b42ea08541cb3ab3aea4045

- re-introduce a genericized NetworkManager
- isolate update logic into a qml accessible class derived from
  NetworkManager
- fix QtWebEngineProcess missing when re-installing over existing
  version
- provide a command line option to override the base url
  for testing local and remote updates
- clean-up manual update-check UI

Gitlab: #101
Change-Id: I9c8d2badae59ec31cab12d38b8470edf2bcad401